[Bash-completion-devel] There is no way to permanently disable completion for a single

Guillaume Rousse guillomovitch at gmail.com
Tue Feb 5 12:58:38 UTC 2013


Le 05/02/2013 13:17, Dr. med. Christoph Gille a écrit :
>
>> Initial Comment:
>> I like having completion for many of the commands that are provided with this
>> package, but some of them have completion that drives me crazy; for example,
>> gdb's command line can be incredibly complex and tab completion on gdb just
>> annoys the bejeebers out of me.
>
> For a system wide effect I would suggest to remove or change permission
> chmod a-r for the respective file in /etc/bash_completion.d/
Which won't change anything for completions dynamically loaded from 
elsewhere, which is the current model for bash-completion 2.0.

I'd rather suggest to run 'complete -r <command>' in a user profile 
script to remove completion declaration, but that's indeed a poor 
workaround.
-- 
BOFH excuse #226:

A star wars satellite accidently blew up the WAN.



More information about the Bash-completion-devel mailing list