-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Would you be interested in a better completion for zsh? #5364
Comments
pip's completion is handled in pip/src/pip/_internal/__init__.py Line 60 in 80b9524
|
Pinging @doronbehar. |
Hmm, I've just installed the latest development version of
Running Here is the output of
|
@doronbehar Yeah, it doesn't complete commands. :( It does complete options though:
Would you be willing to help out with improving pip's autocompletion, though it'd take the form of writing Python code (specifically #5364 (comment)) so that is better? One advantage of doing it in Python is that it's cross shell/platform. |
That's pretty complicated, I don't know python good enough in order to write something like that by myself. Perhaps I would have attempted doing so if the command line arguments parser was written using a |
Yeah. We're planning on switching the CLI to click or argparse in the future, instead of pip's homegrown solution. |
Closing per #11417. |
I've wrote a pretty good completion function of pip for ZSH that I'd would like to contribute.
According to ZSH's completions contribution rules, Completions are not accepted when already available in their original project. Since my completion function uses sub functions for completing sub commands and special options arguments etc, it is rather too complex to be inserted inside src/pip/_internal/commands/completion.py.
I think it would be better to put my completion function in a dedicated file and guide users to put in their
$fpath
. Here is a link to a gist with the whole completion.The text was updated successfully, but these errors were encountered: