[Bash-completion-devel] Non-completions

Ville Skyttä ville.skytta at iki.fi
Mon Feb 7 20:52:12 UTC 2011


Just a thought I've had some time, not sure if it'd be a good idea or not:

What do people think about installing non-completions?  This would be
for commands for which we know the bash default (file) completion is so
bad that not completing at all would be better but we don't have a full
completion for the command yet.

For example, for command "foo" that either does not take an argument or
takes something entirely different than the file names bash would
suggest for it by default:

$ _noop() { true; }
$ complete -F _noop foo
$ foo <TAB>
(nothing)

This should however be combined with at least the redirection stuff
discussed in another thread today so we won't break that.



More information about the Bash-completion-devel mailing list