fix(utils): path_expand always use backslash for windows #3018
Conversation
This file contains 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
jamestrew
force-pushed
the
fix/path-expand-windows
branch
from
b37f49a
to
607d403
Compare
jamestrew
force-pushed
the
fix/path-expand-windows
branch
3 times, most recently
from
96e9b12
to
6717a33
Compare
jamestrew
force-pushed
the
fix/path-expand-windows
branch
from
74d0da8
to
db18f2d
Compare
skip-checks: true
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.
Converts forward slashes on windows to backslashes. Looks like
vim.fn.expandalways did this. I also didn't know sometimes in Windows, you get paths in forward slash (like git) so nowutils.path_expandalways forces backslashes for Windows paths (mostly for plenary compatibility).half closes #2997