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

[latimerio]

> Did you mean ln -s /tmp /tmpX ?

Sorry. Yes I meant   ln -s /tmp  /tmpX.
Thanks for pointing me to do tests as non root.
I usually don't work on the desktop but only do admin tasks over ssh.

We have a link  /applics -> /nfs/AppServer/applics on all our clients.
If I do as regular user:  ls /applics<TAB>   or ll /applics<TAB> , I get a '/' appended as expected in both cases
If I do as root:   ls /applics<TAB>  I also get the '/' appended
  but if I do as root:  ll /applics<TAB>  I get a space appended

Our site has about 250  hosts with HP-UX, RH9, RHEL4, RHEL5, ubuntu 10,
ubuntu 12 and ubuntu 14 (all in LTS) and the described problem only
occurred with the arrival of ubuntu 14.

-- 
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