I know I'm waking up a very old bug here, but I just hit it, on
*trusty*. There was no problem in saucy.
It does seem to match what the original reporter was saying: that it
fails to autocomplete *files* if the directory path has spaces in it. It
will autocomplete subdirectories of directories with spaces in their
names, but not when it gets down to the actual files.
Checked out the workaround in comment #3, but as far as I can make out,
that fix is already in: line 1587 of (now) /usr/share/bash-
completion/bash_completion is:
compopt -o filenames
Of course the offending line may not be the exact number, but it *looks*
like the same thing. So it looks like it may be same symptom, different
cause this time.
NB: This is affecting ls and various other random commands including
personal helper scripts of my own, so I don't think it's completion
rules for specific commands getting in the way.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/883268
Title:
bash ls tab completion broken for files/dirs with spaces in name
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/883268/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
