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

[Peter Cordes]

still can't reproduce.  Is there any chance /nfs/AppServer/applics sometimes looks like a broken symlink?  Do you get the same behaviour if you 
ln -s /tmp /tmpX
and then do your examples exactly as typed?  And ideally, can you do it without writing to /?
mkdir -p test/tmp;  cd test
ln -s ./tmp tmpX
 so I don't have to sudo every time I want to create your testcase, or clean up my system.  This is what I meant by a testcase that works for non-root.

 If this is only reproducible with absolute paths starting with /, then
that might be a clue to something.  I don't *think* mountpoints should
come into this, but I can't reproduce this on my system.  Does root on
your system have anything different in /root/.bashrc?  (or
/root/.profile, if you're in a login shell as root).

 This space-appended behaviour is exactly what's supposed to happen for
a broken symlink, so I still think something about your testcase is
probably weird.  You're not doing completions in a different context
than the command will run, are you?  like complete on one computer a
command that you'll run on another with ssh?

 I know you probably didn't do anything silly like that, but I'm
grasping at straws here.

Prob best if you can just capture some info to upload, from the shell
that's behaving badly:

set > shell_defs.log   # capture all your shell function definitions

set -x
ll /applics[TAB]    # will spew hundreds of lines of shell code tracing
set +x
complete -p ls ll
ls -dl /applics /nfs/AppServer/applics

copy/paste that output to a file.  (or do the above after running
script.  Yes, a program called script, it logs interactive sessions,
default filename is typescript.)

 Err on the side of pasting more stuff, because so far this doesn't make
sense.

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