Fix Gundo for paths with spaces #29
Merged
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
|
Thanks, this fixed my error :) |
|
👍 |
5 tasks
|
I'll merge this once I can get hg-git unfucked. |
|
Thanks! |
dsummersl
added a commit
to dsummersl/gundo.vim
that referenced
this pull request
Nov 27, 2016
[RFC]Rename gundo.vim to mundo.vim
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.
Gundo currently crashes when the plugin is placed on a path that contains spaces due to a failed pyfile command.
The pyfile documentation claims that
The whole argument is used as a single file name., but unfortunately this is not the case. Passing in a path that contains spaces results inE172: Only one file name allowed. We can easily fix this by escaping the directory.