[Bug 482753] Re: bash completion for scp overescapes spaces and does not correctly re-filter ("\\\ " instead of "\ ")

[Martin Eve]

@Thierry: Yes, I see what you mean; scp completion on directories with
other special characters does, indeed, fail with this patch.

It would be nice to have their more complete fix, but (unless we sync
the entire unstable git branch) I don't know how the contrib/ssh
component will interact with the stable bash-completion script.

I would certainly be in favour of such a sync; the current state of scp
completion is unusable.

What do you think?

-- 
bash completion for scp overescapes spaces and does not correctly re-filter ("\\\ " instead of "\ ")
https://bugs.launchpad.net/bugs/482753
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is a direct subscriber.

Status in “bash-completion” package in Ubuntu: Confirmed

Bug description:
Binary package hint: bash-completion

OS: Karmic 9.10

Directory structure on target:

/home/martin/directory 1/directory 2/file.txt

Type:

scp target:/home/martin/directory<TAB><TAB>

Expected:

scp target:/home/martin/directory 1/directory 2/

Actual:

scp target:/home/martin/directory\\\ 1/

To summarise, it is impossible to do any further autocompletion once the \\\ escape sequence has been given.

This is caused by the incorrect line:

		# unescape spaces
		path=${path//\\\\\\\\ / }

in contrib/ssh

It should, instead, read:

		# unescape spaces
		path=${path//\\\\}

Aiming to do a fix for this asap.