Bash completion fails to account for soft links properly: nslater@mahora: ~ $ mkdir -p dir-a/dir-b nslater@mahora: ~ $ ln -s dir-a/dir-b dir-c nslater@mahora: ~ $ touch doc-a nslater@mahora: ~ $ touch doc-b nslater@mahora: ~ $ cd dir-c nslater@mahora: ~/dir-c $ cat ../doc- doc-a doc-b nslater@mahora: ~/dir-c $ cat ../doc-a cat: ../doc-a: No such file or directory nslater@mahora: ~/dir-c $ cat ../doc-ab cat: ../doc-b: No such file or directory
tags 506973 confirmed thanks Hello Noah, This is because it considers "dir-c" as a sibling of dir-a, not as dir-a/dir-b. :( I don't know whether this is fixable or not. Will have a look. Thank you for your report. Kindly, David
Hello A quite old bug, but I may have more precise informations way to reproduce: pablo@desky:~$ mkdir symlink pablo@desky:~$ touch toto pablo@desky:~$ ln -s symlink /tmp/newlink pablo@desky:~$ touch tmp/tutu pablo@desky:~$ cd /tmp/newlink pablo@desky:/tmp/newlink$ cat ../ tutu pablo@desky:/tmp/newlink$ cat ../tutu cat: ../tutu: No such file or directory it looks like bash-completion just looks at the apparent directory structure, and does not follow the target of the links. On the upper example, it checks into /tmp directory instead of checking into $HOME.
Heya, these (#267060 and #506973) are bugs in bash, which it seem aren't going to be fixed anyway, so I'm closing them. David
Heya, these (#267060 and #506973) are bugs in bash, which it seem aren't going to be fixed anyway, so I'm closing them. David