Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ihnp4!ptsfa!ames!hao!husc6!mit-eddie!uw-beaver!ssc-vax!benoni
From: benoni@ssc-vax.UUCP
Newsgroups: comp.sys.apollo
Subject: Re: Aegis Vs. Unix (command retrieval
Message-ID: <1299@ssc-vax.UUCP>
Date: Mon, 15-Jun-87 01:29:04 EDT
Article-I.D.: ssc-vax.1299
Posted: Mon Jun 15 01:29:04 1987
Date-Received: Tue, 16-Jun-87 01:37:24 EDT
References: <8706090628.AA29741@zeus.CS.UCLA.EDU> <1290@ssc-vax.UUCP> <2915@watdragon.UUCP>
Organization: Boeing Aerospace Corp., Seattle WA
Lines: 23

In article <2915@watdragon.UUCP>, hwarkentyne@watdragon.UUCP writes:
> By putting a "hold" on the input window and pressing the "undo"
> button, I could easily recover whole sequences of commands and
> inputs for editing and/or repetition.
> No mousing and only minimal window scrolling is needed.
> I found this method much easier than using the history capability
> of the c-shell.
True. You can backtrack and *that* is useful but by no means an
adequate replacement for the csh history and command line editing features.
Somehow '!v' (= vi anyfile.c) seems relatively easier than searching 
"whole sequences of commands". 
The previous example given however was extolling the virtues of 
"again" something i find of limited use because of the scrolling 
and mousing. 

A particularly nice feature available in csh is upon logging in to
be able to see what your last 25 or so commands were the last time
you were logged on - i am sure with some hacking Apollo's DM might be
able to replicate this - but you will never catch me trading in csh
for the weaker DM.  The point being the csh already has these type of
things built in and i would prefer to write scripts that extend
csh to my needs AND THE SCRIPTS ARE *PORTABLE* TO OTHER 
*NON-APOLLO* MACHINES.