Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site uwvax.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!uwvax!dave
From: dave@uwvax.UUCP (Dave Cohrs)
Newsgroups: net.unix-wizards
Subject: Re: Is 'ksh' available.
Message-ID: <46@uwvax.UUCP>
Date: Sun, 11-Nov-84 18:29:46 EST
Article-I.D.: uwvax.46
Posted: Sun Nov 11 18:29:46 1984
Date-Received: Tue, 13-Nov-84 01:25:08 EST
References: <126@anwar.UUCP> <5720@brl-tgr.ARPA>
Organization: U of Wisconsin CS Dept
Lines: 25

> This means
> we now have shell functions (generalization of csh "alias"),
> built-in "echo" & "pwd" (I fixed the symbolic-link behavior of
> "pwd" for 4.2BSD to act like something sensible instead of
> following ".." literally), and job control.  About the only csh
> feature still lacking is a command history mechanism; probably
> a tcsh-like editing facility but without using termcap would be
> the way to go for this.
> 
> 	Committee to Stamp Out Csh

What? No history?  Listen man, this is probably the one feature I
wouldn't give up from csh.  I hate having to retype commands, especially
when they get long.  If by tcsh editing facility you man yanking/putting
and screen editing, this is fine for stuff on your screen, but not
very useful when the command has scrolled off of your screen, or worse
yet, was something you previously executing 50 commands ago.

	The Committee to Preserve useful 4.2BSD Features
-- 
(Bug?  What bug?  That's a feature!)

Dave Cohrs
...!{allegra,heurikon,ihnp4,seismo,uwm-evax}!uwvax!dave
dave@wisc-rsch.arpa