Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!magnus.ircc.ohio-state.edu!csn!datran2!smb
From: smb@csn.org!datran2
Newsgroups: comp.sys.next
Subject: Re: emacs shell
Keywords: emacs,termcap
Message-ID: <1991Feb14.180404.584@csn.org!datran2>
Date: 14 Feb 91 18:04:04 GMT
References: <2341@mas1.UUCP> <11903@pt.cs.cmu.edu> <1073@kaos.MATH.UCLA.EDU>
Organization: Data Transforms, Inc.
Lines: 25

In article <1073@kaos.MATH.UCLA.EDU> barry@pico.math.ucla.edu (Barry Merriman) writes:
>In article <11903@pt.cs.cmu.edu> ddj@zardoz.club.cc.cmu.edu (Doug DeJulio) writes:
>
>>NeXT machine doesn't have an ordinary CSH, it has CMU's modified CSH
>>with command line editing and other nifty features. 
>
>Where did you learn about this? (man csh?) Does it do all
>the things tcsh does? (filename and command completion, spelling
>correction, editing history list with emacs-style commands, etc).
>

Its really pretty simple, but the documentation is obscure.  You can
read about it at the end of man csh.  The trick is to have a file on
your home directory called ".bindings" that has the shell editing
keys defined.  When you start a csh and it sees this file, the emacs
style command line editing and history become enabled.  Absolutely
critical as far as I'm concerned.

Steve.

-- 
 #====#====#====#====#====#====#====#====#====#====#====#====#====#====#====#
 #  Steve Boker           #  "Badgers, we don't have no stinking badgers"   #
 #  datran2!smb@csn.org   #    -from Treasure of the Sierra Madre Zoo       #
 #====#====#====#====#====#====#====#====#====#====#====#====#====#====#====#