Your message dated Sat, 6 Sep 2008 22:05:08 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: bash_completion: several completions fail to handle
filenames with spaces and other quoted character
has caused the Debian Bug report #259987,
regarding bash_completion does not properly quote characters
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.)
--
259987: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=259987
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: bash
Version: 2.05b-19
Severity: normal
I've noticed that several completions fail when the filename has
characters needing escapes, for example spaces or single quotes. I could
go through and try to provide a comprehensive list of such failed
completions, but I wonder if there is a more systematic way to insure
that irregular filenames don't trip up completion--after all, it works
fine with standard commands like ls and cat.
Just to give two representative examples:
# ls 'some filename with spaces.iso'
some filename with spaces.iso
# cdrecord some<tab>
filename some spaces.iso with
(i.e., improper completion, it thinks the filename is actually four
separate files)
# cdrecord some\ <tab>
becomes
cdrecord some\\\
(and then <tab> again gives no results)
# mount some\ <tab>
(okay)
# sudo mount some\ <tab>
grep: Trailing backslash
grep: Trailing backslash
# sudo mount some\ file<tab>
(same result)
Anyway, that's just two examples, and I'm sure I've experienced others
with other commands. Couldn't a more general approach to escaping be
used so that we don't have to fix these on a case-by-case basis?
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.7-joehill-ethertap
Locale: LANG=en_US, LC_CTYPE=en_US
Versions of packages bash depends on:
ii base-files 3.0.16 Debian base system miscellaneous f
ii libc6 2.3.2.ds1-13 GNU C Library: Shared libraries an
ii libncurses5 5.4-4 Shared libraries for terminal hand
ii passwd 1:4.0.3-29 Change and administer password and
-- no debconf information
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
fixed 259987 20080705
thanks
Hello,
you've been CCed in this mail because you showed interest in bug #259987 [1] in
the Debian BTS, regarding bash-completion (it was in bash, at the time).
I'm sending you this mail because I'm closing the bug: I've just tried all the
cases described in the bugreport, and everything works fine (i.e. spaces, & and
' get correctly quoted, no matter what the command is) -- it seems like
somewhere in these years it has been fixed.
Please, if you happen to re-encounter this bug, feel free to reopen it, sending
a mail to [EMAIL PROTECTED] with:
reopen 259987
thanks
Thanks for your attention,
David Paleino
Bash-Completion Developers.
[1] http://bugs.debian.org/259987
--
. ''`. Debian maintainer | http://wiki.debian.org/DavidPaleino
: :' : Linuxer #334216 --|-- http://www.hanskalabs.net/
`. `'` GPG: 1392B174 ----|---- http://snipr.com/qa_page
`- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174
signature.asc
Description: PGP signature
--- End Message ---
