[Bash-completion-devel] Bug#550676: please make bash-completion falling back to path completion if nothing else is found
Norbert Preining
preining at logic.at
Mon Oct 12 04:12:22 UTC 2009
Package: bash-completion
Version: 1:1.1-1
Severity: normal
Hi David,
it is a bit a pain. As long as not all scenarios are covered bash completion
should fall back to usual normal trivial path completion, and not ignore
or prevent usage.
Recent example:
make KDIR=/lib/mod<TAB><TAB>
give nothing.
Yes
KDIR=/lib/mod<TAB>
does completion, but for make to take it up I have to add it at the END (!!!)
So compiling for a new kernel an out-of-tree module I have to
make KDIR=/lib/modules/2.6.32-rc4
and this is again a case where the completion algorith just walks in your way
and make you feel stupid.
Why not fall back to normal path completion in the case that no other
completion is found? That would leverage a huge class of bugs (some of
which I have filed).
bash-completion should NOT try to be more intelligent than the user, please.
Thanks
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.32-rc3 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages bash-completion depends on:
ii bash 4.0-7 The GNU Bourne Again SHell
bash-completion recommends no packages.
bash-completion suggests no packages.
-- no debconf information
More information about the Bash-completion-devel
mailing list