Fix wrong completion #495
Open
Fix wrong completion #495
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
|
@edolstra @Mic92 @domenkozar @brenoguim Any problem? |
|
No just lack of time. Things will get better next month. |
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.
Sorry for a typo. According to https://zsh.sourceforge.io/Doc/Release/Completion-System.html#Completion-Functions's
_arguments,--long-option[description of option]:name of argument:completion methodshould have 2:s, not 3. Anyone can usepatchelf --set-interpreter <TAB>to trigger this bug. Andpatchelf --print-*should be followed by a elf name: print some information about this elf then exit. So it shouldn't complete any other option(-), but should complete elf name (not(- : *),(*)will stop complete elf name).