I have the same problem. I think it is the same problem as Debian bug #544024 (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544024). In the debian bug report there is a fix that works for me: --- /etc/bash_completion.orig 2009-09-03 08:21:15.229720217 -0400 +++ /etc/bash_completion 2009-09-03 08:21:36.473719600 -0400 @@ -213,6 +213,10 @@ # results in the original argument quote_readline() { + if [ ${BASH_VERSINFO[0]} -gt 3 ]; then + echo "$1" + return + fi local t="${1//\\/\\\\}" echo \'${t//\'/\'\\\'\'}\' #'# Help vim syntax highlighting }
** Bug watch added: Debian Bug tracker #544024 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544024 ** Also affects: bash-completion (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544024 Importance: Unknown Status: Unknown -- Shell autocomplete will not proceed past path with escaped characters https://bugs.launchpad.net/bugs/423446 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
