Use colons rather than asterisks for Vim names #677
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
Internal buffer names are wrapped with asterisks which causes problems on Vim for Windows since it causes the filename globber to be invoked. Using colons works (and also has the benefit of creating an illegal filename, rather than one which is simply unlikely). Signed-off-by: David Allsopp <david.allsopp@metastack.com>
|
Thanks! |
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.
Internal buffer names are wrapped with asterisks which causes problems on Vim for Windows since it causes the filename globber to be invoked. Using colons works (and also has the benefit of creating an illegal filename, rather than one which is simply unlikely).
Without this change, the call to
bot split *merlin-type-history*inmerlin_type.vimcauses an error message and the user's buffer gets the type information instead.