ated to my problem.
Andreas
Paul Jarc wrote:
Andreas Haselbacher <[EMAIL PROTECTED]> wrote:
The first command gave output. Does this mean that command-line
completion was not active?
It means that there were extra completion functions in use, overriding
the default completion beha
The first command gave output. Does this mean that command-line
completion was not active? If yes, how come I could complete paths before?
Andreas
Chet Ramey wrote:
Andreas Haselbacher wrote:
Hi Chet,
I'm afraid I'm not quite sure what you mean. I assume it's installed
becaus
do this by default.
Chet
--
========
Andreas Haselbacher Voice: (217) 333-8683
Center for Simulation of Advanced Rockets Fax: (217) 333-1910
University of Illinois at Urbana-Champaign Email: [EMAIL PROTECTED]
2253 Digital Computer Laboratory, MC 278
1304 West Springfiel
I apologize if this is old hat (I could not find it in the FAQ), but I
encounter the annoying problem that if I use path completion starting
with my home directory, i.e.,
~haselbac/cfd/...
then bash puts a space after each directory name, i.e., if there was a
directory called 'calcs' below 'cfd
