-
-
Notifications
You must be signed in to change notification settings - Fork 662
docs: add shell completion instructions to README #2302
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
Closed
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1 @@ | ||
| Added documentation for shell completions for `pip-compile` and `pip-sync` -- by {user}`Ahmed-AdelB`. |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would rather we didn't instruct users to modify their profile (
~/.bashrcor~/.zshrc), although withfishit's almost unavoidable.I've found many times that
Can we instead provide the
eval-based version of this, and trust that users who need to use the non-eval version know what to do?In particular, I'd like us to imitate the current
clickdocs: https://click.palletsprojects.com/en/stable/shell-completion/#enabling-completionNote that the docs say "add this to
~/.bashrc" and don't provide a command for doing so automatically.So I'd much rather see:
evals to your~/.bashrcevals to your~/.zshrcNot only is fish more complicated to do any other way, it's also a much more niche shell, with typically more advanced users.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When I said "leave the fish doc alone", I meant that the prior version looked correct to me, namely:
The current version is telling people to put the
sourcesnippet into a dedicated completion file, which is a very unusual way to do it and not in line with howclickdocuments this feature.Could you please revert that part?