Debian Bug report logs - #547349
bash-completion: mplayer doesn't complete filenames with spaces it in

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: alex <alex@samad.com.au>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: bash-completion: mplayer doesn't complete filenames with spaces it in

Date: Sat, 19 Sep 2009 06:46:02 +1000

Package: bash-completion
Version: 1:1.0-3
Severity: normal

hi 

if i have 2 files
File name with spaces.mkv
testFile.mkv

completion gets stuck on 
mplayer File\ 


testFile.mkv works


Alex

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing'), (500, 'stable'), (100, 'unstable'), (50, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.30-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash

Versions of packages bash-completion depends on:
ii  bash                          4.0-4      The GNU Bourne Again SHell

bash-completion recommends no packages.

bash-completion suggests no packages.

-- no debconf information

Message #10 received at 547349@bugs.debian.org (full text, mbox, reply):

From: Lars Kruse <devel@sumpfralle.de>

To: 547349@bugs.debian.org

Subject: [bash-completion] "quote_readline" doubles backslashs

Date: Mon, 21 Sep 2009 23:56:37 +0200

[Message part 1 (text/plain, inline)]

Package: bash-completion
Version: 1:1.0-3

--- Please enter the report below this line. ---

Hi,

the function "quote_readline" seems to cause this behavior.

How to reproduce:
 mkdir "foo bar"
 mv foo\ <TAB>
this produces no resulting matches.

bash-completion uses the function "_longopt" in /etc/bash-completion for this
operation. The problem seems to be caused by the output of "quote_readline"
which is called within "_filedir", which is called by "_longopt".

Running dequote/quote_readline does not recover the original input:
 lars@erker:~$ quote_readline "foo\ "
 'foo\\ '
 lars@erker:~$ dequote "$(quote_readline "foo\ ")"
 foo\\ 
(two backslashs instead of one)

In contrast the combination dequote/quote works as expected:
 lars@erker:~$ quote "foo\ "
 'foo\ '
 lars@erker:~$ dequote "$(quote "foo\ ")"
 foo\ 
(one backslash as expected)


I could not understand the difference between "quote" and "quote_readline". But
in the case shown above, "quote" would not cause a problem, while
"quote_readline" does.

Maybe "_filedir" (and "_filedir_xpsec") should use "quote" instead of
"quote_readline"?

thanks for your work,
Lars

--- System information. ---
Architecture: i386
Kernel:       Linux 2.6.30-1-686

Debian Release: squeeze/sid
  990 testing         localhost 

--- Package information. ---
Depends          (Version) | Installed
==========================-+-===============
bash        (>= 3.1dfsg-9) | 4.0-4


Package's Recommends field is empty.

Package's Suggests field is empty.


-- 

gpg key: https://systemausfall.org/schluessel/lars-devel.0.asc

[signature.asc (application/pgp-signature, attachment)]

Send a report that this bug log contains spam.