Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!tut.cis.ohio-state.edu!pt.cs.cmu.edu!lindenthal.cae.ri.cmu.edu!jwb
From: jwb@lindenthal.cae.ri.cmu.edu (John Baugh)
Newsgroups: comp.unix.ultrix
Subject: newcsh is tcsh? [was Re: csh echo problem with backquotes]
Keywords: csh, echo, backquotes
Message-ID: <6727@pt.cs.cmu.edu>
Date: 27 Oct 89 23:09:12 GMT
References: <14174@jumbo.dec.com> <8318@cbmvax.UUCP>
Organization: Carnegie-Mellon University, CS/RI
Lines: 15

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.  Otherwise (when I'm just
typing in a new command), none of the emacs bindings (e.g., ^A, ^E, ...)
work at all.  What am I doing wrong?  I have 'setenv CSHEDIT emacs'
in my .login.

John 'desperately seeking emacs command line editing' Baugh

Note: maybe I don't understand tcsh.  I've been using CMU's csh for
the last couple of years, and was under the impression that they
are similar.