ZSH completions escape #1418
Merged
ZSH completions escape #1418
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
|
I'm unclear why you want to remove it. I had a hard time finding documentation on the |
|
Ah, I had it wrong, looks like |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Completion in ZSH usually escapes spaces and other special characters in file names etc. I think this is the expected behavior.
As I see
-Qhas been introduced in stopthatcow@13b84c5 which fixed sorting. However this options seems unnecessary and unrelated to sort order.Also, I haven't found a straightforward way to test this. In case this breaks something else I'd figure out a way to override the default completion function.