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

[Raphaël]

what about completion interruption.
A way to interrupt the completion process would be nice.

The only way that I know to stop a slow completion (dpkg, ssh, gdb,
...) is to hit Ctrl-C, what looses the line.
Having a kind-of "Ctrl-g" to interrupt the completion process and keep
the line as-is could be an option isn't ?
Or alternatively bash-completion could trap the Ctrl-C signal from bash
(untested).




On Tue, Feb 05, 2013 at 01:58:38PM +0100, Guillaume Rousse wrote:
> 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.