build: switch to plenary.path2 for improved Windows path support #3275
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
jamestrew
changed the title
jamestrew
force-pushed
the
plenary-path2
branch
from
4d90fc1 to
8cbb89a
Compare
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.
Migrating from
plenary.pathtoplenary.path2to solve a bunch of Windows path issuesnvim-lua/plenary.nvim#618
confirmed
closes #3181
closes #3157
closes #2446 (at least with
:set shellslashbut vim generally has poor Windows path support neovim/neovim#3912, vim/vim#541)maybe
closes #3116
closes #3043