Your message dated Wed, 8 Dec 2010 21:29:00 -0600
with message-id <20101209032900.ga4...@burratino>
and subject line Re: bash: Bash does not autocomplete anything after a
backslash on the command prompt
has caused the Debian Bug report #548545,
regarding bash: Bash does not autocomplete anything after a backslash on the
command prompt
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
548545: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=548545
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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 nothing...]
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages bash depends on:
ii base-files 5.0.0 Debian base system miscellaneous f
ii dash 0.5.5.1-3 POSIX-compliant shell
ii debianutils 3.2.1 Miscellaneous utilities specific t
ii libc6 2.9-26 GNU C Library: Shared libraries
ii libncurses5 5.7+20090803-2 shared libraries for terminal hand
Versions of packages bash recommends:
pn bash-completion <none> (no description available)
Versions of packages bash suggests:
pn bash-doc <none> (no description available)
-- no debconf information
--- End Message ---
--- Begin Message ---
tags 548545 - moreinfo
quit
Stephen Dranger wrote:
> It seems to be okay now.
I hate to let a perfectly good mystery go, but I suppose that means
we should close the bug.
> Installing bash-complete didn't help at the
> time, by the way.
Yes, bash-completion had a well understood bug in this area. :)
(Bug#544024)
Thanks much.
Jonathan
--- End Message ---
