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

latimerio 1372286 at bugs.launchpad.net
Tue Dec 9 09:52:13 UTC 2014


I have a freshly installed ubuntu 14.04.1 LTS and it also shows the problem.
Thus I doubt that it a legacy package.
I found that it occurs repeatable with symlinks and aliased commands as shown below

TEST SCENARIO
 ln -s /tmpX   /tmp
 alias ll='ls -l'

ls /tmp<TAB>           # gives "tmp/" and "tmpX/"  without trailing spaces on a new line
ll /tmp<TAB>            # ditto

ls /tmpX<TAB>        # completes to "ls /tmpX/"  on the same line

#BUT
ll /tmpX<TAB>         # gives "ll /tmpX "   with a trailing space thus breaking further completion

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



More information about the foundations-bugs mailing list