[Bug 177243] Re: Bash command completion puts backslash in front of beginning dollar sign
Keith Thompson
177243 at bugs.launchpad.net
Fri Apr 27 01:17:06 UTC 2012
I'm seeing this on Ubuntu 12.04. (I installed beta2 a couple of weeks
ago and have applied all updates since then).
I have commented out the entire body of
/etc/profile.d/bash_completion.sh (due to a different issue).
With a newly created account, no changes to any $HOME/.* files :
$ uname -a
Linux kvetch 3.2.0-23-generic-pae #36-Ubuntu SMP Tue Apr 10 22:19:09 UTC 2012 i686 i686 i386 GNU/Linux
$ echo $BASH_VERSION
4.2.24(1)-release
$ dpkg -l bash bash-completion
[SNIP]
ii bash 4.2-2ubuntu2 GNU Bourne Again SHell
ii bash-completio 1:1.3-1ubuntu8 programmable completion for the bash shell
$ echo $HOME/<tab>
produces
$ echo \$HOME/
--
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/177243
Title:
Bash command completion puts backslash in front of beginning dollar
sign
Status in “bash-completion” package in Ubuntu:
Fix Released
Status in “bash-completion” package in Debian:
Fix Released
Bug description:
Command completion inserts a backslash in front of the beginning
collar sign of my environment variable. Example:
export MYENVVARB=xxx
cd $MYE<tab>
results in
cd \$MYENVVARB
which is not only seriously inconvenient, but I've never seen any
standard Bash configuration that does it. I recommend it be
configured or programmed otherwise. Perhaps there is a special mode
for this, but it should not be turned on in the terminal. Those
terminals are places where environment variables will be used a lot,
and people will want command completion for them. This is completely
non-standard. I'm seeing it in both the standard terminals, and in
the xterms I use.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/177243/+subscriptions
More information about the foundations-bugs
mailing list