-
-
Notifications
You must be signed in to change notification settings - Fork 4.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
Adding bash command completion #1000
Comments
It'd be interesting to see how much of an overhead it becomes. 100 commands might not be a problem, but if there's 10,000 of them, then it might be problematic. |
Sorry, the overhead I meant was not when building this list, but when bash parsed it originally, and then whenever you |
if it's alphabetically sorted, I can't imagine it will be too expensive to traverse... |
I just tested with around 8000 items. Seems to work pretty fine. |
Wooooh #1000 |
Yes |
Hello,
I think adding command completion would be a nice feature addition to this project.
Adding it is very simple as we just have to place a file in
/etc/bash-completion.d/
and bash will source it everytime it loads (For zsh also, its something similar although I haven't researched much about it). The problem is the file needs to have the list of all commands that are present.Now, this is something I wanted to discuss about. I believe the responsibility of placing the file in the folder (
/etc/bash_completion.d/
) goes to the respective clients. So, I propose creating a completion file 'tldr', which will get updated with each push (through another function added inscripts/build.sh
), and keeping it in thescripts
folder. After this, every client will pull the file and place it in that folder in the install step.Does this seem reasonable ?
The text was updated successfully, but these errors were encountered: