Xref: utzoo comp.unix.amiga:1009 comp.unix.shell:2439 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!pdn!palan!ckctpa!crash From: crash@ckctpa.UUCP (Frank J. Edwards) Newsgroups: comp.unix.amiga,comp.unix.shell Subject: Re: SVR4 /bin/sh BUG Message-ID: <1991Jun18.151835.2068@ckctpa.UUCP> Date: 18 Jun 91 15:18:35 GMT References: <1991Jun15.014909.1562@menudo.uh.edu> <1991Jun15.141609.848@ckctpa.UUCP> <1991Jun17.234824.20461@jato.jpl.nasa.gov> Organization: Edwards & Edwards Consulting Lines: 33 In article <1991Jun17.234824.20461@jato.jpl.nasa.gov> dave@jato.jpl.nasa.gov writes: >crash@ckctpa.UUCP (Frank J. Edwards) writes: >>Why do *you* use csh? What are the advantages (please be specific and >>objective) of csh over ksh? > >Ksh doesn't have filename completion. (At least not that I know of) >This is from a person who uses ksh, csh, and tcsh. Ah, but it does! When in the editing mode, ie. hit if you've set EDITOR=vi, you can type the following characters for fname completion: * Causes a * to be appended to the current word and filename generation to be attempted. If no match is found, ring the bell. Otherwise replace the word with the matching file(s). \ Filename completion. Replaces the current word with the longest common prefix of all filenames matching the current word if an asterisk had been appended. If the match is unique: a / is appended if its a directory, a space otherwise. = List the filenames that would be generated by "*", above. >Dave Hayes - Network & Communications Engineering - JPL / NASA - Pasadena CA >dave@elxr.jpl.nasa.gov dave@jato.jpl.nasa.gov ames!elroy!dxh [PS: Thanks folks -- I kinda' expected "flames galore" from this request, but that hasn't been the case (of course, my mail was redirect to /dev/null :-) ] -- Frank J. Edwards | "I did make up my own mind -- there 2677 Arjay Court | simply WASN'T ANY OTHER choice!" Palm Harbor, FL 34684-4504 | -- Me Phone (813) 786-3675 (voice) | Only Amiga Makes It Possible...