NetNews Usenet Archive 1992 #27/NN_1992_27.iso/spool/gnu/bash/bug/661

Text File | 1992-11-21 | 1.7 KB | 42 lines

Newsgroups: gnu.bash.bug
Path: sparky!uunet!cis.ohio-state.edu!casbah.acns.nwu.edu!navarra
From: [e-mail] (John Navarra)
Subject: Re: Question about path name expansion
Message-ID: <[e-mail]>
Sender: [e-mail]
Organization: Northwestern University, Evanston Illinois.
References: <[e-mail]>
Distribution: gnu
Date: Sat, 21 Nov 1992 06:28:30 GMT
Approved: [e-mail]
Lines: 28

In article <[e-mail]> [e-mail] (Bjoern Wennberg) writes:
>When I hit <TAB> as the first character typed, bash 'almost' hangs forever
>trying to figure out which command I was trying to invoke.
>
>Is there a way to make bash recognise that a tab was the first character typed
>and just do nothing ?
>
Hear Hear! I agree wholeheartedly!

Actually, I like the way zsh does this. You hit TAB, you get TAB. It knows
when you want to do TAB completion (because it has a default set of
commands that is does certain completions on; and, you can include your
own set of commands and patterns to do hostname completion for example)

TAB has always worked nicely for me in zsh and I don't have to worry about
binding keys to do other types of completion.

However, just as an observation, if I inadvertently hit TAB at the bol in
bash, I can ^C and it will no longer hang.

-tms

--
You can get further with a kind word | You can get further with a kind word
and a gun than a kind word alone.    | and a phaser than a kind word and a gun.
          --al capone                |           -- John Navarra
=======From the Lab of the MaD [e-mail]========