[Bash-completion-devel] [bash-completion-Bugs][313100] Completion of paths after ls command is not working correctly since version 1.3

[bash-completion-bugs at alioth.debian.org]

Bugs item #313100, was opened at 28.04.2011 09:45
You can respond by visiting: 
https://alioth.debian.org/tracker/?func=detail&atid=413095&aid=313100&group_id=100114

Status: Open
Priority: 3
Submitted By: Nobody (None)
Assigned to: Nobody (None)
Summary: Completion of paths after ls command is not working correctly since version 1.3 
Distribution: Fedora / Red Hat
Originally reported in: None
Milestone: 1.3
Status: None
Original bug number: 


Initial Comment:
Since I updated to bash completion 1.3 completion of paths does not work correctly for ls. Example:

> mkdir -p 'abc/uvw xyz'

with version 1.2

> ls ab<tab>

results in

> ls abc/

which can be extended for the second directory

> ls abc/u<tab>

to 

> ls abc/uvw\ xyz/

with version 1.3 I get for the first completion

> ls ab<tab>

this

> ls abc 

with a trailing space. If a remove the space manually and add a '/' instead I can again continue

> ls abc/u<tab>

but get

> ls abc/uvw xyz 

without the escape '\' before the space in the directory name and again a trailing space.

----------------------------------------------------------------------

You can respond by visiting: 
https://alioth.debian.org/tracker/?func=detail&atid=413095&aid=313100&group_id=100114