Okay, this is a TOTALLY trivial question in the scheme of things, but if anybody has an answer it would remove a little daily annoyance from my life.
I use quite a lot of symlinks to organize directories on my disks, but keep falling foul of needing to do an extra tab when using bash completion. To clarify, let's say I had the following file in a directory:
I could type "cat /f", hit tab, press d, then hit tab and return.
However, if /files/ is a symlink, when I type "cat /f" and hit tab, instead of completing the input as far as "cat /files/", it completes only to "cat /files" and I have either to do an extra tab or add the slash myself. I'd be interested in anybody can explain why the system behaves this way, and also if there's some way to avoid needing to remember the extra tab when using symlink directories.
As I say, I know it's trivial, but I'm constantly tripping up over this.
Last edited by olembe (2011-01-26 20:05:51)
set mark-symlinked-directories on
Last edited by olembe (2011-01-26 20:05:39)
gah yet another config file I will have to fiddle with
pretty cool tho, thanks for posting the solution.
by now my ~/.inputrc contained only this line
set completion-ignore-case On
it makes the filename matching of <TAB> case insensitive. like this:
$ ls foo bar BAZ $ cat b<TAB><TAB> bar BAZ $cat ba<TAB> $cat BAZ
now it will contain one more line
I like your line a lot. That's going in my .inputrc right now!