[Bug 177243] Re: Bash command completion puts backslash in front of beginning dollar sign

[nacorn]

Note: in contrast, on Ubuntu 10.04 with
GNU bash, version 4.1.5(1)-release (i486-pc-linux-gnu)

I do not get the backslash:

repro:
sudo mv /etc/bash_completion /etc/bash_completion.backup
sudo mv /etc/bash_completion.d /etc/bash_completion.d.backup
env -i HOME=$HOME DISPLAY="$DISPLAY" xterm -e bash --login --noprofile --norc

in new xterm:

bash-4.2$ cd $HOME<tab>
bash-4.2$ cd $HOME <cursor> <--- just adds a space (same as Ubuntu 12.04)

bash-4.2$ cd $HOME/<tab>
bash-4.2$ cd /home/acorn/              <--- no bug! expands as expected!

bash-4.2$ xyz $HOME/<tab>
bash-4.2$ xyz /home/acorn            <--- no bug! expands as expected!

So maybe this is a regression in bash itself?

-- 
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