I have been using tcsh for a long time on Red Hat Linux boxes, and
bash on other UNIX-boxes. One thing I really love with tcsh is the
I can swiftly operate using the <TAB> to do auto-complete, when
a deep directory hierarchy. I have that...
With bash I surely could use your skills to improve my usage of bash
(read; allow me to ditch tcsh fully).
I have an annoying bash-problem on Red Hat Linux 5.x. If I e.g. try
to a subdirectory of another directory (e.g. $HOME), where the
"cd $HOME<TAB>" is expanded to "cd /home/pto " (without the quotes).
I get $HOME expanded - quite ok - but I get an annoying space efter
I will never like that space, I strongly prefer if I could get
"cd $HOME<TAB>" expanded to "cd /home/pto/" (without the quotes) so
continue to press <TAB> and see the allowed sub-directories - much
I have also understood I can do
$ complete -o nospace cd
to change the mode of operation, but this seems to disable the
function when doing cd $VARIABLE<TAB>.
I am guestimating, that you have discussed this in February
but the February archive seems to be lost;
so I cannot get the details of it.
That cited link is suggesting; "ESC ctrl-e gets rid of the
backslash, and if you want to keep the $VAR as $VAR, backspace over
the terminal space and continue. Or you can ESC ctrl-e again, and
convert the $VAR to its value, so you won't need to repeat the
ESC ctrl-e for each further <tab>."
which IMHO is not really what I want.
Any hints on this? Can I set the mode of operation as I like where
infamous space is replaced by a slash when doing "cd ... <TAB>"?
Peter Toft, PhD