Neat csh feature

[John Lacey]

In article <3574 at uokmax.UUCP> jkmedcal at uokmax.UUCP (Jeff K Medcalf) writes:
>In article <62079 at linus.UUCP> rtidd at mitre.arpa (Randy Tidd) writes:
>> [about file name completion in csh.]
>
>This is both true and elegant.  However, cat v* will do the same thing.
> [ ... ]
>The shell may expand with some wierdness under some circumstances, though.

This last warning is more of a danger than you suppose. File completion will
behave differently if the given sequence is not unique.  In that case, at
best wildcards will give an error (i.e., cd) but `cat v*' where v is not
unique will be unpleasant.  File completion using <ESC> will tell you 
when you press escape whether the given sequence is unique, and you can 
make it so, without causing some unexpected to happen.  This is especially
handy as file completion will work on any pathname, and you get interactive
feedback at checking the name, without having to ls the other directory.

So, these tools really are orthogonal---use wildcards to specify multiple
files matching a pattern, and file completion to shorten the typing of
long names.


-- 
John Lacey     lacey at tcgould.tn.cornell.edu    cornell!batcomputer!lacey

After August 16:  jjlacey at owucomcn.bitnet
If you have to, try  mdl at sppy00.UUCP or maybe {...}!osu-cis!sppy00!mdl