Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!cs.utexas.edu!uunet!cbmvax!grr
From: grr@cbmvax.UUCP (George Robbins)
Newsgroups: comp.unix.ultrix
Subject: Re: newcsh is tcsh? [was Re: csh echo problem with backquotes]
Keywords: csh, echo, backquotes
Message-ID: <8338@cbmvax.UUCP>
Date: 28 Oct 89 19:42:43 GMT
References: <14174@jumbo.dec.com> <8318@cbmvax.UUCP> <6727@pt.cs.cmu.edu>
Reply-To: grr@cbmvax.UUCP (George Robbins)
Organization: Commodore Technology, West Chester, PA
Lines: 22

In article <6727@pt.cs.cmu.edu> jwb@lindenthal.cae.ri.cmu.edu (John Baugh) writes:
> In article <8318@cbmvax.UUCP> grr@cbmvax.UUCP (George Robbins) writes:
> >release or use the /usr/new/csh (aka tcsh) which hasn't been improved in
> 
> /usr/new/csh is tcsh?  I'm using it but it doesn't seem to behave
> like tcsh.  For example, emacs line editing works only when I do
> an ESC to retrieve the previous command.

Maybe one should say "a tcsh".  I don't know the exact derivation of the
Ultrix /usr/new/csh, but prior to 3.x, it did command completion, which
the tcsh on our sun's did and then in 3.x, it sprouted command line
editing.  You may get some different action by applying the "tcsh patches"
to the Berkeley csh source, I dunno.  I don't use these features myself,
but it does seem to satisfy the desire for command completion that our Sun
users expect...

See man newcsh and /usr/new/Readme.newcsh for details.

-- 
George Robbins - now working for,	uucp: {uunet|pyramid|rutgers}!cbmvax!grr
but no way officially representing	arpa: cbmvax!grr@uunet.uu.net
Commodore, Engineering Department	fone: 215-431-9255 (only by moonlite)