Yeah, I'm not seeing the OP's bug at all, even when sourcing Trusty's
unmodified bash_completion.
The directories inside quotes problem is a different thing. Marked as
fixed, prob. by upstream ages ago.
** Changed in: bash-completion (Ubuntu)
Status: Confirmed => Fix Released
--
You re
works for me, at least after applying the fix for bug 1387057 (properly
quoting "$quoted"). On Trusty. This is probably the same bug.
Or maybe not: I'm seeing
$ echo ./"./foo[TAB] turns into
$ echo ./"././foo
every [TAB] adds another ./
foo does get expanded to the longest common prefix of
I can confirm too.
I have run some more tests.
First one, i have deactivated the bash-completion to see how bash work
with quotes "
USE CASE:
$ touch "foo bar"
$ mv " # work
foo bar
$ mv "f # work
foo bar
$ mv ' # work
foo bar
$ mv 'f # work
foo bar
$ nano "
I checked this and confirm that it is happening as described in the bug.
I too am not sure if there is any reason behind this. Would be glad to
hear from someone.
** Changed in: bash-completion (Ubuntu)
Status: New => Confirmed
--
No tab completion when using quote (")
https://bugs.launc
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/19700126/Dependencies.txt
--
No tab completion when using quote (")
https://bugs.launchpad.net/bugs/298799
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
