Debian Bug report logs - #468254
bash-completion: strange behavior on ls and spaces

Toggle useless messages

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

From: Michael Musenbrock <redeamer@gmx.net>

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

Subject: bash-completion: strange behavior on ls and spaces

Date: Thu, 28 Feb 2008 00:24:47 +0100

Package: bash-completion
Version: 20060301-2
Severity: important

I've installed the bash-completion package and now i've some strange
behavior on the completing path- and filenames with commands like ls,
cp or move.

I give you an example for better understanding:

ls /my/ 2xtab --> works
ls /my/folder 2xtab --> works
ls /my/folder/some\ subfolder/ 2xtab --> does not work any more

And, as far as I know, filepath completion isn't done (or were not be
done yet) by sourcing /etc/bash_completion in, so all in all, this type
of completion shouldn't get affected by a new /etc/bash_completion,
which is the only real thing, what this new package is updating.

Kind regards,
Michael

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.24-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages bash-completion depends on:
ii  bash                          3.1dfsg-9  The GNU Bourne Again SHell
ii  ucf                           3.005      Update Configuration File: preserv

bash-completion recommends no packages.

-- no debconf information

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

From: Didier Raboud <didier@raboud.com>

To: Michael Musenbrock <redeamer@gmx.net>

Cc: 468254@bugs.debian.org

Subject: Re: bash-completion: strange behavior on ls and spaces

Date: Fri, 29 Feb 2008 09:56:49 +0100

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

Le jeudi, 28 février 2008 00.24:47, vous avez écrit :
> Package: bash-completion
> Version: 20060301-2
> Severity: important
>
> I've installed the bash-completion package and now i've some strange
> behavior on the completing path- and filenames with commands like ls,
> cp or move.
>
> I give you an example for better understanding:
>
> ls /my/ 2xtab --> works
> ls /my/folder 2xtab --> works
> ls /my/folder/some\ subfolder/ 2xtab --> does not work any more
>
> And, as far as I know, filepath completion isn't done (or were not be
> done yet) by sourcing /etc/bash_completion in, so all in all, this type
> of completion shouldn't get affected by a new /etc/bash_completion,
> which is the only real thing, what this new package is updating.
>
> Kind regards,
> Michael

Hi, 

I confirm this exact behavior on my box.

Regards, 

Didier

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

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

From: "Udi Meiri" <meiri3@netvision.net.il>

To: 468254@bugs.debian.org

Subject: Re: bash-completion: strange behavior on ls and spaces

Date: Sat, 1 Mar 2008 18:28:36 +0200

Also, typing "ls \ " and pressing tab gives:
"ls \\\ "
With another tab:
"ls \\\\\\\ "
and so on...

-- 
- Udi

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

From: Luk Claes <luk@debian.org>

To: Didier Raboud <didier@raboud.com>, 468254@bugs.debian.org

Cc: Michael Musenbrock <redeamer@gmx.net>

Subject: Re: Bug#468254: bash-completion: strange behavior on ls and spaces

Date: Sun, 02 Mar 2008 16:06:37 +0100

tags 468254 unreproducible
thanks

Didier Raboud wrote:
> Le jeudi, 28 février 2008 00.24:47, vous avez écrit :
>> Package: bash-completion
>> Version: 20060301-2
>> Severity: important
>>
>> I've installed the bash-completion package and now i've some strange
>> behavior on the completing path- and filenames with commands like ls,
>> cp or move.
>>
>> I give you an example for better understanding:
>>
>> ls /my/ 2xtab --> works
>> ls /my/folder 2xtab --> works
>> ls /my/folder/some\ subfolder/ 2xtab --> does not work any more

Sorry, but I can't reproduce this.

>> And, as far as I know, filepath completion isn't done (or were not be
>> done yet) by sourcing /etc/bash_completion in, so all in all, this type
>> of completion shouldn't get affected by a new /etc/bash_completion,
>> which is the only real thing, what this new package is updating.

So, maybe it's related to some other change outside bash-completion?
I'll look into it some more, we'll see if I can find anything...

You both did agree to update the /etc/bash_completion file with the
maintainer's one, right?

Cheers

Luk

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

From: Luk Claes <luk@debian.org>

To: Udi Meiri <meiri3@netvision.net.il>, 468254@bugs.debian.org

Subject: Re: Bug#468254: bash-completion: strange behavior on ls and spaces

Date: Sun, 02 Mar 2008 16:09:32 +0100

Udi Meiri wrote:
> Also, typing "ls \ " and pressing tab gives:
> "ls \\\ "
> With another tab:
> "ls \\\\\\\ "
> and so on...

Unfortunately I can't reproduce this.

You did agree to update the /etc/bash_completion file with the
maintainer's version during installation of bash-completion, right?

Cheers

Luk

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

From: EspeonEefi <espeoneefi@eep.dnsalias.org>

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

Subject: bash_completion broken for arguments with spaces; problem in _get_cword()

Date: Sun, 02 Mar 2008 10:59:56 -0500

Package: bash-completion
Version: 20060301-2
Followup-For: Bug #468254

This bug is actually breaking completion of all arguments that have
embedded spaces, whether escaped with \ or within quotes. This bug
causes completion to be run against just the part of the current word
after the last space.

I believe the problem is in _get_cword() (line 185 in
/etc/bash_completion). More specifically, its method of finding where
the current word starts is broken. Line 190

    word_start=`expr "$cur" : '.*['"${COMP_WORDBREAKS}"']'`

is supposed to find that position, but the regular expression is too
greedy, and it captures all the way up to the last space, whether that
space is really the beginning of the word or actually an escaped space
or a space inside quotes that should be considered part of the word.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages bash-completion depends on:
ii  bash                          3.1dfsg-9  The GNU Bourne Again SHell
ii  ucf                           3.005      Update Configuration File: preserv

bash-completion recommends no packages.

-- no debconf information

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

From: Luk Claes <luk@debian.org>

To: EspeonEefi <espeoneefi@eep.dnsalias.org>, 468254@bugs.debian.org

Subject: Re: Bug#468254: bash_completion broken for arguments with spaces; problem in _get_cword()

Date: Sun, 02 Mar 2008 17:19:03 +0100

EspeonEefi wrote:

> This bug is actually breaking completion of all arguments that have
> embedded spaces, whether escaped with \ or within quotes. This bug
> causes completion to be run against just the part of the current word
> after the last space.

I don't see how it is related, I still can't reproduce the test cases
they showed...

> I believe the problem is in _get_cword() (line 185 in
> /etc/bash_completion). More specifically, its method of finding where
> the current word starts is broken. Line 190
> 
>     word_start=`expr "$cur" : '.*['"${COMP_WORDBREAKS}"']'`
> 
> is supposed to find that position, but the regular expression is too
> greedy, and it captures all the way up to the last space, whether that
> space is really the beginning of the word or actually an escaped space
> or a space inside quotes that should be considered part of the word.

Did this work before or is this a feature request? Anyway, I would be
happy to include a patch fixing it.

Cheers

Luk

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

From: EspeonEefi <espeoneefi@eep.dnsalias.org>

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

Subject: Re: Bug#468254: bash_completion broken for arguments with spaces; problem in _get_cword()

Date: Sun, 02 Mar 2008 12:18:32 -0500

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

Package: bash-completion
Version: 20060301-2
Followup-For: Bug #468254

I can reproduce the test cases on my machine. I've attached my current
/etc/bash_completion just to check against yours. It's the result of
purging bash-completion and then reinstalling bash-completion, so it
should be the maininter's version that's shipping with bash-completion.

Running a diff between the /etc/bash_completion from bash-completion and
the /etc/bash_completion from bash 3.1dfsg-8 shows that basically
everywhere that had "cur=${COMP_WORDS[$COMP_CWORD]}" was replaced by
"cur=`_get_cword`". (_get_cword() did not exist in the bash_completion
from bash 3.1dfsg-8.) Changing references to _get_cword back to
${COMP_WORDS[$COMP_CWORD]} fixes the problem.

The _get_cword is new functionality that the new bash_completion is
trying to provide. Supposedly, by using _get_cword instead of
${COMP_WORDS[$COMP_CWORD]}, it will match against the current word only
up to the insertion point instead of against the entire current word.
However, the new "feature" has introduced quite a regression that makes
completion unusable if you have any number of files with spaces in their
names.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages bash-completion depends on:
ii  bash                          3.1dfsg-9  The GNU Bourne Again SHell
ii  ucf                           3.005      Update Configuration File: preserv

bash-completion recommends no packages.

-- no debconf information

[bash_completion (text/x-pascal, attachment)]

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

From: Luk Claes <luk@debian.org>

To: EspeonEefi <espeoneefi@eep.dnsalias.org>, 468254@bugs.debian.org

Subject: Re: Bug#468254: bash_completion broken for arguments with spaces; problem in _get_cword()

Date: Sun, 02 Mar 2008 18:42:31 +0100

EspeonEefi wrote:
> Package: bash-completion
> Version: 20060301-2
> Followup-For: Bug #468254
> 
> I can reproduce the test cases on my machine. I've attached my current
> /etc/bash_completion just to check against yours. It's the result of
> purging bash-completion and then reinstalling bash-completion, so it
> should be the maininter's version that's shipping with bash-completion.

Your version of bash_completion is indeed the same as mine.

> Running a diff between the /etc/bash_completion from bash-completion and
> the /etc/bash_completion from bash 3.1dfsg-8 shows that basically
> everywhere that had "cur=${COMP_WORDS[$COMP_CWORD]}" was replaced by
> "cur=`_get_cword`". (_get_cword() did not exist in the bash_completion
> from bash 3.1dfsg-8.) Changing references to _get_cword back to
> ${COMP_WORDS[$COMP_CWORD]} fixes the problem.

Well, apparently I don't understand what the problem is. Can you please
provide a step by step test case?

> The _get_cword is new functionality that the new bash_completion is
> trying to provide. Supposedly, by using _get_cword instead of
> ${COMP_WORDS[$COMP_CWORD]}, it will match against the current word only
> up to the insertion point instead of against the entire current word.

Yes, that's something I can reproduce. Though I don't see how that's
related to the test cases the other users submited as that only happens
when the cursor is positioned in the middle of a word instead of at the end?

> However, the new "feature" has introduced quite a regression that makes
> completion unusable if you have any number of files with spaces in their
> names.

Without being able to reproduce it I'm not so sure it's a bug in the new
feature or a bug in some part of the environment...

Cheers

Luk

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

From: EspeonEefi <espeoneefi@eep.dnsalias.org>

To: Luk Claes <luk@debian.org>

Cc: 468254@bugs.debian.org

Subject: Re: Bug#468254: bash_completion broken for arguments with spaces; problem in _get_cword()

Date: Sun, 02 Mar 2008 13:31:37 -0500

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

On Sun, 2008-03-02 at 18:42 +0100, Luk Claes wrote:
> Your version of bash_completion is indeed the same as mine.

Hrm... I've attached my ~/.bashrc as well to make sure that isn't the
cause, either.

I suspect that /etc/bash_completion isn't getting loaded for some
reason. Perhaps add an echo to the top of /etc/bash_completion, start a
new shell, and make sure that the echo shows up? (Another thing to see
is that with that /etc/bash_completion, you should be getting the
message "bash: complete: kpdf: no completion specification" every time
you start a new shell.)

> > from bash 3.1dfsg-8.) Changing references to _get_cword back to
> > ${COMP_WORDS[$COMP_CWORD]} fixes the problem.
> 
> Well, apparently I don't understand what the problem is. Can you please
> provide a step by step test case?

mkdir test
cd test
touch 'foo bar'
ls foo\ b<tab>

Instead of properly completing 'foo bar', bash finds no completions and
beeps at you.

mkdir test
cd test
touch 'foo bar'
touch baz
ls foo\ b<tab>

In this case, bash completes 'foo\ b' to 'baz'!

What's happening is that the old ${COMP_WORDS[$COMP_CWORD]} would
provide 'foo\ b' to match against. The new _get_cword() will match only
from the last space because that expr regex is too greedy, so it will
provide just 'b' to match against.

-- eefi

[.bashrc (text/plain, attachment)]

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

From: Deng Xiyue <manphiz-guest@users.alioth.debian.org>

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

Subject: I got the same symptom

Date: Mon, 03 Mar 2008 14:37:59 +0800

Package: bash-completion
Version: 20060301-2
Followup-For: Bug #468254

I have the same symptom described above, both the failed and false
completion containing backslash and the duplication of backslash.  I
can confirm that /etc/bash_completion is sourced by noticing

bash: complete: kpdf: no completion specification

on a new bash instance.

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (300, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
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-completion depends on:
ii  bash                          3.1dfsg-9  The GNU Bourne Again SHell
ii  ucf                           3.005      Update Configuration File: preserv

bash-completion recommends no packages.

-- no debconf information

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

From: Didier Raboud <didier@raboud.com>

To: Luk Claes <luk@debian.org>

Cc: 468254@bugs.debian.org, Michael Musenbrock <redeamer@gmx.net>

Subject: Re: Bug#468254: bash-completion: strange behavior on ls and spaces

Date: Tue, 4 Mar 2008 15:19:37 +0100

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

Le dimanche, 2 mars 2008 16.06:37 Luk Claes, vous avez écrit :
> Sorry, but I can't reproduce this.
>
> >> And, as far as I know, filepath completion isn't done (or were not be
> >> done yet) by sourcing /etc/bash_completion in, so all in all, this type
> >> of completion shouldn't get affected by a new /etc/bash_completion,
> >> which is the only real thing, what this new package is updating.
>
> So, maybe it's related to some other change outside bash-completion?
> I'll look into it some more, we'll see if I can find anything...
>
> You both did agree to update the /etc/bash_completion file with the
> maintainer's one, right?
>
> Cheers
>
> Luk

Hi, 

I just tried to reinstall bash-completion and I thought to a way to reproduce 
this :

$ cd /tmp
$ mkdir 'with space'
$ cd wit[TAB]		[it works]
$ cd with\ space/
$ ls			[empty]
$ mkdir 'an other'
$ cd ..
$ cd wit[TAB]		[it works again]
$ cd with\ space/[TAB]	[NOTHING happens] [then delete 4 cars]
$ cd with\ sp[TAB]	[it does not work anymore]

Regards, 

Didier

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

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

From: Ross Burton <ross@burtonini.com>

To: 468254@bugs.debian.org

Subject: Re: bash-completion: strange behavior on ls and spaces

Date: Wed, 05 Mar 2008 14:09:17 +0000

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

Add me to the list of people who see this.
-- 
Ross Burton                                 mail: ross@burtonini.com
                                          jabber: ross@burtonini.com
                                     www: http://www.burtonini.com./
 PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF

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

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

From: Andrei Paskevich <andrei@capet.iut-fbleau.fr>

To: 468254@bugs.debian.org

Subject: Re: bash-completion: strange behavior on ls and spaces

Date: Wed, 12 Mar 2008 01:04:00 +0200

The problem can be partially cured by the following one-line 
change in _get_cword:

=====================================================================
--- bash_completion.old     2008-03-12 00:52:00.000000000 +0200
+++ /etc/bash_completion        2008-03-12 00:53:23.000000000 +0200
@@ -188,7 +188,7 @@
     local word_start
 
     cur=${COMP_LINE:0:$COMP_POINT}
-    word_start=`expr "$cur" : '.*['"${COMP_WORDBREAKS}"']'`
+    word_start=`expr "$cur" : '.*[^\\]['"${COMP_WORDBREAKS}"']'`
     cur=${cur:$word_start}
     echo $cur
 }
=====================================================================

You will still have a problem with completing a quote-protected 
string with spaces:

% ls "foo b<tab>

but in the default case (backslash protection) everything should
work fine:

% ls foo\ b<tab>
% ls foo\ bar

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

From: Christian Pernegger <pernegger@gmail.com>

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

Subject: bash-completion: me too (filename completion completely shot)

Date: Tue, 18 Mar 2008 15:24:17 +0100

Package: bash-completion
Version: 20060301-3
Followup-For: Bug #468254


I have it, too, and that's on a relatively fresh lenny install. At the
time of the install bash-completion was not in testing but when it
dropped in I installed it ASAP because I've very much grown used to
this feature on my other boxes.

So, hitting [TAB] after anything with a '\' (escaping backslash) in it
breaks, same for anything with a ' ' (space) in it. The other escaping
method via quotes doesn't work either, i. e.

$ cmd "ab c [TAB]

gives a garbled result as well.

Regards,

C.


-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.22-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_AT.UTF-8, LC_CTYPE=de_AT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages bash-completion depends on:
ii  bash                          3.1dfsg-9  The GNU Bourne Again SHell
ii  ucf                           3.005      Update Configuration File: preserv

bash-completion recommends no packages.

-- no debconf information

Message #84 received at 468254-close@bugs.debian.org (full text, mbox, reply):

From: Luk Claes <luk@debian.org>

To: 468254-close@bugs.debian.org

Subject: Bug#468254: fixed in bash-completion 20060301-4

Date: Sat, 22 Mar 2008 23:32:03 +0000

Source: bash-completion
Source-Version: 20060301-4

We believe that the bug you reported is fixed in the latest version of
bash-completion, which is due to be installed in the Debian FTP archive:

bash-completion_20060301-4.diff.gz
  to pool/main/b/bash-completion/bash-completion_20060301-4.diff.gz
bash-completion_20060301-4.dsc
  to pool/main/b/bash-completion/bash-completion_20060301-4.dsc
bash-completion_20060301-4_all.deb
  to pool/main/b/bash-completion/bash-completion_20060301-4_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 468254@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Luk Claes <luk@debian.org> (supplier of updated bash-completion package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Sat, 22 Mar 2008 23:10:30 +0000
Source: bash-completion
Binary: bash-completion
Architecture: source all
Version: 20060301-4
Distribution: unstable
Urgency: low
Maintainer: Luk Claes <luk@debian.org>
Changed-By: Luk Claes <luk@debian.org>
Description: 
 bash-completion - programmable completion for the bash shell
Closes: 351913 400380 435117 452083 468254 471249 471666
Changes: 
 bash-completion (20060301-4) unstable; urgency=low
 .
   * Add some fixes from Ubuntu:
   * Fix completion of filenames with spaces (Closes: #468254).
   * Fix parsing of SSH config files (Closes: #435117).
   * Change priority to standard (Closes: #471666).
   * Add some more completions for xine (Closes: #452083, #471249).
   * Fix completion of gzip (Closes: #351913).
   * Also use $HOSTFILE in hostname completion (Closes: #400380).
Files: 
 fc6044de38a50106afe4ea189ecbc723 592 shells standard bash-completion_20060301-4.dsc
 44d19c6288759aad898392a1b2571845 13499 shells standard bash-completion_20060301-4.diff.gz
 580fdd7af5ae0cd55ec8b5639633447e 123842 shells standard bash-completion_20060301-4_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFH5ZJ75UTeB5t8Mo0RAjYlAJ9M+FfedlFVPXRoGLqrbr0qr31sIQCeJfkn
sJXecOvVhOnC7tqIuqSjdJk=
=oxfs
-----END PGP SIGNATURE-----

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

From: Andrei Paskevich <andrei@capet.iut-fbleau.fr>

To: 468254@bugs.debian.org

Subject: _get_cword drops spaces at the end of the completion word

Date: Sun, 23 Mar 2008 21:00:45 +0200

Please, put $cur in double quotes in the last 'echo' in _get_cword:
====================================================================
--- /usr/share/bash/bash_completion     2008-03-23 01:09:58.000000000 +0200
+++ /etc/bash_completion        2008-03-23 20:56:42.000000000 +0200
@@ -211,7 +211,7 @@
 
 
        cur=${cur:$word_start}
-       echo $cur
+       echo "$cur"
 }


====================================================================

Otherwise, spaces at the end of the completion word get dropped:
% touch 'I first'
% touch 'II second'
% ls I\ <tab>           # won't be completed to 'I first'

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

From: Antonio Ospite <ospite@studenti.unina.it>

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

Subject: bash-completion: We still need to quote $cur properly

Date: Thu, 24 Apr 2008 11:58:19 +0200

Package: bash-completion
Version: 20060301-4
Followup-For: Bug #468254


Hi,

please apply the latest change from Andrei Paskevich in #468254, it fixes
another issue I have, which I guess it's the same Andrei described.

Without quoting $cur properly:

  ~ $ mkdir -p /tmp/sandbox && cd /tmp/sandbox
  /tmp/sandbox $ touch test
  /tmp/sandbox $ touch test\ 2
  /tmp/sandbox $ mv test\ <TAB>
  test    test 2
  /tmp/sandbox $ mv test 
                        ^cursor here

INCORRECT, it should complete to "test 2"

After I changed 'echo $cur' to 'echo "$cur"' as Andrei suggested:

  ~ $ mkdir -p /tmp/sandbox && cd /tmp/sandbox
  /tmp/sandbox $ touch test
  /tmp/sandbox $ touch test\ 2
  /tmp/sandbox $ mv test\ <TAB>
  /tmp/sandbox $ mv test\ 2 
                            ^cursor here

CORRECT!

Thanks,
   Antonio

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages bash-completion depends on:
ii  bash                          3.2-2      The GNU Bourne Again SHell
ii  ucf                           3.006      Update Configuration File: preserv

bash-completion recommends no packages.

-- no debconf information

Message #101 received at 468254-quiet@bugs.debian.org (full text, mbox, reply):

From: David Paleino <d.paleino@gmail.com>

To: 468254-quiet@bugs.debian.org

Cc: Bash-Completion Developers <bash-completion-devel@lists.alioth.debian.org>

Subject: Reopening #468254

Date: Sun, 11 May 2008 17:46:10 +0200

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

reopen 468254
thanks

Hi,
I'm reopening this bug since there are many other bugreports which report more
or less the same issues.
I suggest leaving this report open until we completely fix this.

Kindly,
David

-- 
 . ''`.  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 (application/pgp-signature, attachment)]

Message #108 received at 468254-close@bugs.debian.org (full text, mbox, reply):

From: Luk Claes <luk@debian.org>

To: 468254-close@bugs.debian.org

Subject: Bug#468254: fixed in bash-completion 20080617

Date: Sat, 21 Jun 2008 21:02:04 +0000

Source: bash-completion
Source-Version: 20080617

We believe that the bug you reported is fixed in the latest version of
bash-completion, which is due to be installed in the Debian FTP archive:

bash-completion_20080617.dsc
  to pool/main/b/bash-completion/bash-completion_20080617.dsc
bash-completion_20080617.tar.gz
  to pool/main/b/bash-completion/bash-completion_20080617.tar.gz
bash-completion_20080617_all.deb
  to pool/main/b/bash-completion/bash-completion_20080617_all.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 468254@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Luk Claes <luk@debian.org> (supplier of updated bash-completion package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Sat, 21 Jun 2008 21:59:43 +0200
Source: bash-completion
Binary: bash-completion
Architecture: source all
Version: 20080617
Distribution: unstable
Urgency: low
Maintainer: Bash Completion Maintainers <bash-completion-devel@lists.debian.org>
Changed-By: Luk Claes <luk@debian.org>
Description: 
 bash-completion - programmable completion for the bash shell
Closes: 347316 365658 376433 394636 404976 409423 416655 424736 428641 432289 441017 455510 468254 470539 470742 472132 472940 474094 474517 474974 475242 478596 480879
Changes: 
 bash-completion (20080617) unstable; urgency=low
 .
   [ David Paleino ]
   * New upstream release
     - add more completions to aptitude (Closes: #432289)
     - fixed UTF-8 problem with _get_cword(), thanks to
       Andrei Paskevich (Closes: #472132)
     - fixed autoremove completion, thanks to Flavio Visentin
       (Closes: #474974)
     - cmf and CMF added to playmidi completion (Closes: #365658)
     - added rrdtool completion, thanks to Justin Pryzby (Closes: #428641)
     - added OpenDocument completion for unzip/zipinfo (.od{f,g,p,s,t})
       (Closes: #472940)
     - fixed escaping problems with job control (i.e. disown, jobs, bg,
       fg): the argument is now surrounded by "" (Closes: #347316)
     - make mkdir complete also on filenames (Closes: #376433)
     - {bz,z}{cat,cmp,diff,egrep,fgrep,grep,less,more} now should complete
       on all filenames, not just compressed archives (just commented out)
       (Closes: #455510)
     - fixes Perl completion (Closes: #470742)
     - fixes get_cword -> _get_cword typo (Closes: #478596)
     - fixes _get_cword() function to properly handle filenames with
       whitespaces (Closes: #394636, #468254, #474094)
     - added .pdf.bz2 completion to evince (Closes: #424736)
     - added .svg completion to display (Closes: #441017)
     - added .m2ts completion to mplayer (Closes: #480879)
     - added extra/dh_bash-completion to ease future rewrite of bc.
   * debian/copyright - now in a fancier machine-parsable format.
   * debian/control:
     - added myself to Uploaders
     - debhelper Build-Depends updated to >= 6.
   * debian/watch:
     - improved current watch line regex
     - added (commented out) probable future watch line
   * debian/compat bumped to 6
   * debian/dirs, debian/install and debian/links added
   * debian/rules:
     - refactored to make use of debian/{dirs,install,links}
 .
   [ Steve Kemp ]
   * Applied patch to fix completion of umount command.
     (Closes: #470539)
   * Fixed the completion of Perl manpages.
     (Closes: #404976)
   * Added 'aif' to the filenames offed for completion for mplayer.
     (Closes: #474517)
   * Allow tsocks completion.
     (Closes: #409423)
   * Update mutt completion to handle local usernames.
     (Closes: #416655)
   * Update apt-get completion to include the flag "--no-install-recommends"
     (Closes: #475242)
Checksums-Sha1: 
 a267866b73de860449ddbc4374faa0b27cb14652 854 bash-completion_20080617.dsc
 d0fc2f36ee0d896f98c1e5dfd49e8623bb936aaa 97143 bash-completion_20080617.tar.gz
 91dc4ad723ecbff302047187e65f6aefedf5ebbf 83372 bash-completion_20080617_all.deb
Checksums-Sha256: 
 9aa0ed60aa9fc88fcc3a542a0d296ead12c23dbae025d158ff414267b22c960b 854 bash-completion_20080617.dsc
 57cd6ee1abc39182183eebeeb1378bdd2438363bf766d69dcabd0320378b6b22 97143 bash-completion_20080617.tar.gz
 e88bd724c2e44629c27fe0346369fe450f0cae12f846ae08fc3794b7dcb1ae32 83372 bash-completion_20080617_all.deb
Files: 
 058c2c5c7a2da8c58f3fbf4f117caf26 854 shells standard bash-completion_20080617.dsc
 902c045bb9fce960571f44200b476cec 97143 shells standard bash-completion_20080617.tar.gz
 7997031028650ef5f5ae30bf1ba5488f 83372 shells standard bash-completion_20080617_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkhdZpQACgkQ5UTeB5t8Mo2n+ACcC7WR8B82ilcQ7iB69fQ/SLQ7
BAwAn3aAUrB08bRSg5QD3/wF9qdPGtC0
=CoOt
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.