[Bug 1387057] Re: wildcard incorrect completion
Peter Cordes
peter at cordes.ca
Fri Nov 28 12:24:33 UTC 2014
The problem is a lack of quoting in
/usr/share/bash_completion/bash_completion.
set -x revealed where the problem happens: in a compgen -X -f. $quoted
is used without quotes, so it expands, and you get the first of however
many glob expansions.
There are two unquoted uses of $quoted in _filedir(). Fixing them
fixed my tab-expanding-globs problem.
Don't forget to apply the fix for bug 1390061, too. Another case of
lack of quoting leading to code that doesn't do what was intended.
** Changed in: bash-completion (Ubuntu)
Status: New => Confirmed
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to bash-completion in Ubuntu.
https://bugs.launchpad.net/bugs/1387057
Title:
wildcard incorrect completion
Status in bash-completion package in Ubuntu:
Confirmed
Bug description:
steps to reproduce (verified on trusty)
$ touch /tmp/file01.txt;touch /tmp/file11.txt
$ file /tmp/fileTAB
file01.txt file02.txt
$ file /tmp/file*TAB
the last command will then incorrectly complete to
$ file /tmp/file01.txt
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1387057/+subscriptions
More information about the foundations-bugs
mailing list