peterd@naxos:~/tmp$ mkdir foo
peterd@naxos:~/tmp$ mkdir bar
peterd@naxos:~/tmp$ cd bar
peterd@naxos:~/tmp/bar$ mkdir baz
peterd@naxos:~/tmp/bar$ ln -s ../foo foo
peterd@naxos:~/tmp/bar$ cd foo
peterd@naxos:~/tmp/bar/foo$ ls ../ba
Hit Tab, completes incorrectly:
peterd@naxos:~/tmp/bar/foo$ ls ../baz
ls: cannot access ../baz: No such file or directory
peterd@naxos:~/tmp/bar/foo$ cd ../ba
Hit Tab, does not offer any completion. Must type explicitly:
peterd@naxos:~/tmp/bar/foo$ cd ../baz
peterd@naxos:~/tmp/bar/baz$
So not only does it offer the wrong completion for `ls`, but it fails to
offer that completion for `cd`, for which it would be correct!
(Actually, it seems to offer the completion for `cd` if you have not
sourced /etc/bash_completion, but does not if you have sourced
/etc/bash_completion.)
This bug has been around for a long time, and I keep expecting it to get
fixed because it is so glaring. Needs reporting I guess.