fix: previewing and editing files on windows #214
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
closes #204
There are a lot of problems with special characters and
:edit
on Windows. neovim/neovim#3912 and vim/vim#541I think that with the current utilities, there is literally no way to make
:edit
behave properly in all cases. As an example, on Windows::edit fname$PATH.txt
will expand the$PATH
variable, leading to a garbage filename:edit fname\$PATH.txt
will treat the\
as a path separator, causingfname
to be a directory and$PATH.txt
the file within it.I'm trying to work around this issue entirely by using
bufadd
to load the file path directly as a buffer, then using the:buffer
command to switch to it. Preliminary results look good, but it needs more testing because I'm not at all confident that:buffer
will run all the same autocmds and have all the same side effects as:edit
.