Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Nice, but..' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Nice, but..
Authored by: sjk on Jul 21, '02 12:37:29AM

I wonder if the mark-directories variable in the readline library interacts/interfers with that. I have "set mark-directories off" in ~/.inputrc because I don't like trailing slashes appended to directories; wish there were also a way to nuke trailing spaces, like "unset addsuffix" in tcsh.

tcsh is still my primary interactive shell, but more recent features like programmable completion in bash tempt me to switch. There are a few tcsh features I utilize in tcsh (e.g. the wordchars variable to set word boundaries) that don't have bash equivalents (yet), but it's really that trailing space appended to filenames after completion that's the biggest issue to full-time conversion.



[ Reply to This | # ]
tcsh has similar (was: Nice, but..)
Authored by: duff on Jul 22, '02 12:28:09AM
tcsh is still my primary interactive shell, but more recent features like programmable completion in bash tempt me to switch.
I haven't looked at the package (as I don't use bash), but I do have programmable completion setup for tcsh. It's done with the 'complete' command and you can override default completion for commands, argument numbers given to commands or even arguments followed by certain options for certain commands -- the completion can be provided either by saying e.g. files ending with .tex to the cammand pdflatex, "just directories" for arguments followed by -I for gcc or by giving a shell variable to use as list or even a command to execute (and use the result as a list of matches). But it's really a mess to setup (man tcsh if you want to have a go at it), but I'd expect it isn't much simpler for bash... this is unix in all its beauty...

[ Reply to This | # ]