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

[Peter Cordes]

If we can figure out if there's one bad file that is commonly left lying
around, and breaks things, a workaround can be shipped in bash-
completion to blacklist it.

 I'm going to close any pre-trusty reports of this, since they're
probably the acroread crap.  And point those bugs to here.

I editted the title and description to make this bug be about what I
think is probably the root cause.  If you come across something that
doesn't fit into what this bug is now, probably filing a new bug would
be the best thing to do.


** Summary changed:

- unwanted space after directory completion
+ unwanted space after directory completion (probably old cruft after upgrades)

** Description changed:

- With bash-completion 2.1 the default for "unknown" commands seems to be to add a space after a string.
- Thus path name completion cannot be performed properly.
- Various users have complained about this for specific commands.
+ 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].
  
- The reason behind bash-completion is to make life easier.
- So the default should always be the more ergonomic solution.
+ Testcase copied from bug 1000470, which I'm closing because it was
+ probably from acroread.sh, which is now blacklisted.
  
- In most cases the added space requires a backspace, a '/' and another tab press.
- This is awkward and much worse than manually entering space when necessary.
+ Extra space scenario:
+ find /op<TAB> ==> find /opt<Space>
  
- So please change the default for pathname completion back to the
- behaviour of bash_completion 1.3.
+ 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.

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

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