Actually, ignore the question about "complete -p bash", it's not
relevant here.
But if you instead could try to run bash with verbose diagnostics on for
a while, that might be useful.
The verbose diagnostics will spew out stuff on the terminal when you
attempt completion, as well as when commands execute. You enable it
with "set -vx" and turn it off with "set +vx".
Like this:
vnix$ set -vx
echo -ne "\033]0;[EMAIL PROTECTED]: ${PWD/$HOME/~}\007"
++ echo -ne '\033]0;[EMAIL PROTECTED]: ~\007'
vnix$ echo $HOM<TAB>
vnix$ echo $HOME<RET>
+ echo /home/era
/home/era
echo -ne "\033]0;[EMAIL PROTECTED]: ${PWD/$HOME/~}\007"
++ echo -ne '\033]0;[EMAIL PROTECTED]: ~\007'
vnix$ cd $HOM<tab>
+ local 'IFS=
' 'cur=$HOM' i j k
+ [[ $HOM == ?(\\)\$* ]]
+ COMPREPLY=($( compgen -v -P '$' -- "${cur#?(\\)$}" ))
compgen -v -P '$' -- "${cur#?(\\)$}"
++ compgen -v -P '$' -- HOM
+ return 0
\$HOME
vnix$ cd \$HOME<RET>
+ cd '$HOME'
bash: cd: $HOME: No such file or directory
echo -ne "\033]0;[EMAIL PROTECTED]: ${PWD/$HOME/~}\007"
++ echo -ne '\033]0;[EMAIL PROTECTED]: ~\007'
vnix$ set +vx
set +vx
+ set +vx
vnix$
--
UbuntuME: Bash command completion puts backslash in front of beginning dollar
sign
https://bugs.launchpad.net/bugs/177243
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
