This bug seems to affect 17.10 too. 3+ years and going on strong.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387057
Title:
wildcard incorrect completion
To manage notifications about this bug g
In addition to the unquoted "$quoted" that @peter-cordes mentioned,
there's another bug in the _filedir() function:
--- /usr/share/bash-completion/bash_completion--OLD 2015-08-19
19:58:22.734667377 -0500
+++ /usr/share/bash-completion/bash_completion 2016-01-05
15:56:50.442988910 -0
** Changed in: bash-completion (Ubuntu)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1387057
Title:
wildcard incorrect completion
To manage notifications about t
Thanks, Peter.
The problem is still the same at least for vivid. I can't see the
relevant upstream bug at the moment which is only visible to logged in
members. If there is something to backport, we should.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
submitted upstream as
https://alioth.debian.org/tracker/index.php?func=detail&aid=314891&group_id=100114&atid=413095
bug 1390061 is fixed upstream, as a side-effect of reworking the
relevant code.
** Bug watch added: alioth.debian.org/ #314891
http://alioth.debian.org/support/tracker.php?aid=
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 _filedi
