$HOME is a good example as a testcase, but a terrible example of it
actually being a problem, because ~/file.txt is easier to type anyway.
$OLDPWD is more annoying. I think progcomp used to expand the variable
on your cmdline, and then of course completion just worked normally. I
think that
This is a REGRESSION. It used to expand $variable to its value rather than
generating \$variable
So, for example, if file.txt exists in $HOME, typing
ls $HOME/filtab
used to generate
ls /home/user/file.txt
but now gives you
ls \$HOME/file.txt
which is useless.
Either it should be
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bash-completion (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/890913
reported upstream:
http://alioth.debian.org/tracker/index.php?func=detailaid=313501group_id=100114atid=413095
** Bug watch added: alioth.debian.org/ #313501
http://alioth.debian.org/support/tracker.php?aid=313501
** Also affects: bash-completion (Fedora) via
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a regular (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
