Oh forgot to mention, you can toggle programmable completion on or off with shopt -u progcomp # unset shopt -s progcomp # set
Usually bash's builtin file/directory completion gets it right, and doesn't trip up on unusual characters in filenames (e.g. 'foo*' leads to problems with progcomp.) When progcomp does something weird, it's useful to see if bash-builtin completion does what you expect. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1372286 Title: unwanted space after directory completion (probably old cruft after upgrades) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1372286/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
