[Bug 1372286] Re: unwanted space after directory completion (probably old cruft after upgrades)

[latimerio]

Sorry for not getting back earlier.
I think I have found the cause for the problem at our site.

As I said we have a mixed environment with different versions of ubuntu and redhat.
In our common bashrc there is a check if  the variable $BASH_COMPLETION is set.
On Redhat and until ubuntu 12 this variable gets set to /etc/bash_completion if  bash_completion is sourced.
This is not the case with ubuntu 14 so our bashrc  sources some legacy bash_completion from an NFS mount.

For ubuntu 14 this legacy stuff adds the trailing space in our case.

Thus I think this bug can be closed.

Nonetheless I'd like to know if there is way to detect if
bash_completion is already sourced other than checking the
BASH_COMPLETION variable.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to bash-completion in Ubuntu.
https://bugs.launchpad.net/bugs/1372286

Title:
  unwanted space after directory completion (probably old cruft after
  upgrades)

Status in bash-completion package in Ubuntu:
  Confirmed

Bug description:
  With bash-completion 2.1, some users are seeing broken completion for
  directories, with a space being added at the end, requiring a
  [BACKSPACE]/[TAB].

  Testcase copied from bug 1000470, which I'm closing because it was
  probably from acroread.sh, which is now blacklisted.

  Extra space scenario:
  find /op<TAB> ==> find /opt<Space>

  Backslash scenario:
  cd ~
  mkdir -p test\ 1/test
  find test\ 1/t<TAB>
  find test 1/test
  find: `test': No such file or directory
  find: `1/test': No such file or directory

  
  This bug can get closed when we find out what other old files get left in /etc/bash_completion.d and cause problems, so we can blacklist them, too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1372286/+subscriptions