🚀 go-pugleaf

In <1992Jul24.142605.16455@gmuvax2.gmu.edu> rjackson@gmuvax2.gmu.edu (Richard L Jackson Jr) writes:

>|> I did a simple comparison of CSH and KSH.  I am asking this
>|> group for solutions to csh feature that ksh appears to lack.
>|> I am using ULTRIX 4.1, VAX 8530.
>|> 
>|> 1) set filec or file completion

>In ksh, using vi-style command line editing, try

><ESC>* or <ESC>\ 

>where <ESC> is the ESCAPE key.
>There is a slight difference.  I'm not a tcsh user, but users tell
>me that <ESC>\ is quite similar to tcsh's file name completion.

>In ksh, using emacs-style command line editing, try

><ESC><ESC>

One more thing... In BASH, in either editing mode, you can start typing
in the name of a file, then hit <TAB>, and if the shell can complete it
with an existing file, it will print them and add a space. If not, it
will list the files that match if * were appended to it.

So let's say you have these files in a directory:
-rw-r--r--  1 tim          3180 Jul 28 10:46 3_ai.doc
-rw-r--r--  1 tim          2565 Jul 28 10:47 3_ai_1.doc
-rw-r--r--  1 tim         11451 Jul 28 10:48 3_ai_2.doc
-rw-r--r--  1 tim          4675 Jul 28 10:49 3_ai_3.doc

If you type:
more 3_<TAB>

the shell will list the matching files for you: 
3_ai.doc    3_ai_2.doc
3_ai_1.doc  3_ai_3.doc  

If you type in some more characters, you'll get:
You > more 3_ai_1<TAB>
BASH> more 3_ai_1.doc

If you type in the name of a directory instead of a file, 
BASH will complete that directory name and add '/'.

-- 
 --------------------------
|Timothy J. Shelling, CmpE |"Paired opposites define your longings --
|  tim@mal-s2.gatech.edu   |  and those longings imprison you."
| gt2540b@prism.gatech.edu |				    -- Zensunni Whip