home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.amiga
- Path: sparky!uunet!usc!sol.ctr.columbia.edu!destroyer!ncar!csn!kbsw1!jose
- From: jose@kbsw1 (Jose Sousa 806 9999)
- Subject: Re: Broken term? sag?
- Message-ID: <1992Aug28.192133.15423@kbsw1>
- Date: Fri, 28 Aug 1992 19:21:33 GMT
- Distribution: usa
- Reply-To: jose@kbsw2.UUCP (Jose Sousa 806 9999)
- References: <23061@hacgate.SCG.HAC.COM> <BtoK0J.86J@agora.rain.com> <1992Aug28.140829.4440@isc-br.isc-br.com>
- Organization: Kentek Information Systems
- Lines: 20
-
- In article <1992Aug28.140829.4440@isc-br.isc-br.com> ricks@odin.isc-br.com (Rick Schaeffer 99) writes:
- >In article <BtoK0J.86J@agora.rain.com> chuff@agora.rain.com (Chris Hufnagel) writes:
- >>In article <23061@hacgate.SCG.HAC.COM> johnl@SDFSERV.hac.com (John Lee) writes:
- >>>
- >>>I don't think "ksh" and I'm positive that "csh" can't handle command-line
- >>>editing in this fashion (using cursor keys/escape combinations.) The
- >>>
- >
- >I dunno about csh, but ksh *does* do command line editing. You have to
- >do "set -o emacs" in your .profile (or "set -o vi"
-
- Ksh uses 'ed' by default. You can use 'set -o ...' to set the editor ksh uses.
- Another way is to set the environment variable EDITOR to your favorite editor.
- Thus in your .profile do EDITOR=vi or EDITOR=emacs and export it. Ksh will
- the use the specified editor.
- ( You may need to set EDITOR=/<path_to_editor>/vi )
- All this stuff is documented in the ksh man entry.
-
- Jose A. Sousa
- Kentek Information Systems jose@kentek.com
-