Fix weird path problem with cygwin vim #1
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
On cygwin, the processing of root path is somewhat different from unix systems:
/ and // are considered different things, and vim's filereadable() will return true for paths beginning with //.
Thus the approach of simplify(currentpath . '/..') won't work since it will produce a // path when current path is /.
This pull request add a cygwin-specific fix for this problem, only with a special has("win32unix") flag to make it only affect cygwin vim (and maybe also vim under msys, which I doubt anyone really uses it).