Added compatibility with suda.vim plugin #100
Open
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
|
Great man, I just did something similar without realizing there was an open pull request. I hope they accept it. |
isaacItz
approved these changes
Jan 13, 2021
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.
suda.vim is a plugin which lets you open files with sudo by using a protocol prefix, and/or automatically when opening a file that is missing read or write permissions.
Because the file path in vim is changed to
suda://[the file path]this was causing the program to pass non-existent paths to range, causing it to immediately exit. So this compatibility patch just removes that prefix if suda is installed.I don't have any experience with vimscript but I don't think there should be any issues on such a small change. I moved the path code into its own function to prevent repeat code.