Fix error when opening new files containing quotes #41
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
`vim-fetch` gave this error when opening a new file that contained
quotes:
Error detected while processing VimEnter Autocommands for "*":
E116: Invalid arguments for function fetch#buffer
For example, `vim '"ok".txt'` would give an error if `"ok".txt` didn't
exist.
This was happening because the quotes weren't being properly escaped.
This fixes that and removes the error.
I tested this with my personal configuration and on a completely fresh
virtual machine.
|
Thank you for fixing this |
Owner
|
merged thanks. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
vim-fetchgave this error when opening a new file that contained quotes:For example,
vim '"ok".txt'would give an error if"ok".txtdidn't exist.This was happening because the quotes weren't being properly escaped. This fixes that and removes the error.
I tested this with my personal configuration and on a completely fresh virtual machine.