Path: utzoo!utgpu!water!watmath!clyde!bellcore!tness7!killer!mit-eddie!bloom-beacon!tut.cis.ohio-state.edu!lvc
From: lvc@tut.cis.ohio-state.edu (Lawrence V. Cipriani)
Newsgroups: comp.unix.wizards
Subject: Re: ksh history editing
Message-ID: <14120@tut.cis.ohio-state.edu>
Date: 24 May 88 19:24:29 GMT
References: <2599@usceast.UUCP> <2601@usceast.UUCP> <4095@mtgzz.UUCP> <2199@quacky.mips.COM> <4108@mtgzz.UUCP> <10012@tekecs.TEK.COM> <10249@agate.BERKELEY.EDU>
Organization: The Ohio State University Dept of Computer and Information Science
Lines: 11

In article <10249@agate.BERKELEY.EDU> ked@garnet.berkeley.edu (Charles Faulhaber) writes:
>The MKS Toolkit version of ksh for MSDOS allows you to specify
>the editor to be used for command editing.

The *command line* editing capabilities are either vi or emacs.
The *command* editing can be be defined with $FCEDIT.
Didn't the original question had to do with *command line* editing?
-- 
Larry Cipriani, AT&T Network Systems and Ohio State University
Domain: lvc@tut.cis.ohio-state.edu
Path: ...!cbosgd!osu-cis!tut.cis.ohio-state.edu!lvc (weird but right)