Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rutgers!mit-eddie!uw-beaver!teknowledge-vaxc!mkhaw
From: mkhaw@teknowledge-vaxc.ARPA (Michael Khaw)
Newsgroups: comp.unix.questions
Subject: Re: vms vs unix
Message-ID: <12970@teknowledge-vaxc.ARPA>
Date: Thu, 21-May-87 12:54:27 EDT
Article-I.D.: teknowle.12970
Posted: Thu May 21 12:54:27 1987
Date-Received: Sat, 23-May-87 11:59:45 EDT
References: <7494@brl-adm.ARPA>
Organization: Teknowledge, Inc., Palo Alto CA
Lines: 20

in article <7494@brl-adm.ARPA>, SULLIVAN%suny-bing.csnet@RELAY.CS.NET says:
> Regardless of limits on the number of commands remembered, the command
> editing facility of vms (invoked with up-arrow) is one of the few things
> really nice about vms.  Shell-writers' alert!  such a facility would be a

Ksh is not a standard component of 4bsd/Ultrix, but you can get it, and it
does history editing using your choice of emacs or vi commands (unfortunately
you lose filename completion via ESC, because emacs uses ESC a lot).  It uses
arrow keys to move fore/backwards in the history list, and is not tied to
vt100s.

I suppose it's more user-friendly and arguably more "obvious" to handle command
history a la ksh or vms dcl, but I find the arcane csh history syntax oddly
more productive.

Mike Khaw
-- 
internet:  mkhaw@teknowledge-vaxc.arpa
usenet:	   {hplabs|sun|ucbvax|decwrl|sri-unix}!mkhaw%teknowledge-vaxc.arpa
USnail:	   Teknowledge Inc, 1850 Embarcadero Rd, POB 10119, Palo Alto, CA 94303