Bug#548545: bash: Bash does not autocomplete anything after a backslash on the command prompt

2010-12-08 Thread Jonathan Nieder
tags 548545 + moreinfo unreproducible quit Jonathan Nieder wrote: Can you still reproduce this problem (perhaps with bash from snapshot.debian.org)? Can't reproduce with bash 4.0-7 (on i386), either, alas. :( -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a

Bug#548545: bash: Bash does not autocomplete anything after a backslash on the command prompt

2010-12-08 Thread Stephen Dranger
It seems to be okay now. Installing bash-complete didn't help at the time, by the way. On Wed, Dec 8, 2010 at 9:19 PM, Jonathan Nieder jrnie...@gmail.com wrote: tags 548545 + moreinfo unreproducible quit Jonathan Nieder wrote: Can you still reproduce this problem (perhaps with bash from

Bug#548545: bash: Bash does not autocomplete anything after a backslash on the command prompt

2010-11-02 Thread Jonathan Nieder
Hi Stephen, Thanks for reporting, and sorry for the long silence. On 2009-09-26, Stephen Dranger wrote: When typing on the bash command line, bash refuses to give a list of possible autocompletions if there is any backslash-escaped characters already on the line. For example: $ foo [hit

Bug#548545: bash: Bash does not autocomplete anything after a backslash on the command prompt

2009-09-26 Thread Stephen Dranger
Package: bash Version: 4.0-7 Severity: important When typing on the bash command line, bash refuses to give a list of possible autocompletions if there is any backslash-escaped characters already on the line. For example: $ foo [hit TAB] foo/bar foo foo/foo bar $ foo/bar\ [hit TAB] [does