[Bash-completion-devel] Bug#551707: bash-completion: does not complete dlocate

Norbert Preining preining at logic.at
Sun Dec 27 21:07:45 UTC 2009

On Sun, 27 Dec 2009, David Paleino wrote:
> tags 551707 unreproducible

Strange. I had bash-completion purged from my system.

Now I installed it.

Then I did
	dlocate /usr/s<TAB><TAB>
and again nothing nothing nothing.

Can you guarantee that you are not using something else then what there
is in the sid repository???

Please tell me what info I can provide to debug that, but I have to
purge bash-completion until you ask me, because currently it is as
useful as a keyboard filled with coke.

> > Again, that would be solved by what I have reported in another bug, namely
> > that bash-completion defaults to path completion if nothing else can be
> > found ....
> I believe this would involve changing each completion, providing "compgen -f" 
> in COMPREPLY if nothing is found.

Well, still that is something that might be interesting, maybe implemented
in a different way.

The point here is that if nothing is found, maybe the completion 
algorithm is incomplete ... or forgot some options ... you never know
in what ways people abuse the system. And then it should fall back
to what normal bash would do by default, namely complete the path.

Best wishes


Norbert Preining                preining@{jaist.ac.jp, logic.at, debian.org}
JAIST, Japan               TU Wien, Austria            Debian TeX Task Force
gpg DSA: 0x09C5B094   fp: 14DF 2E6C 0307 BE6D AD76  A9C0 D2BF 4AA3 09C5 B094
Sort of person who takes the lift to travel one floor.
			--- Douglas Adams, The Meaning of Liff

More information about the Bash-completion-devel mailing list