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 TAB] > foo/bar foo > foo/foo bar > > $ foo/bar\ [hit TAB] > [does nothing...] [...] > pn bash-completion <none> (no description available) Can you still reproduce this problem (perhaps with bash from snapshot.debian.org)? Josh and ricky were talking about bash-completion bug http://bugs.debian.org/544024 as far as I can tell, but since you did not have bash-completion installed, something else might be involed. Thoughts? Jonathan -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
