Path: utzoo!attcan!uunet!cs.utexas.edu!texbell!splut!jay
From: jay@splut.conmicro.com (Jay "you ignorant splut!" Maynard)
Newsgroups: comp.unix.microport
Subject: Re: ksh / emacsmode ???
Message-ID: <-LX&QBM@splut.conmicro.com>
Date: 1 Aug 90 10:16:54 GMT
References: <1990Jul29.141650.26386@kth.se> <5KV&Z9C@splut.conmicro.com> <1990Jul30.202358.11116@kth.se>
Reply-To: jay@splut.conmicro.com (Jay "you ignorant splut!" Maynard)
Organization: Confederate Microsystems, League City, TX
Lines: 30

In article <1990Jul30.202358.11116@kth.se> perand@admin.kth.se (Per Andersson) writes:
>In article <5KV&Z9C@splut.conmicro.com> jay@splut.conmicro.com (Jay "you ignorant splut!" Maynard) writes:
>>In article <1990Jul29.141650.26386@kth.se> perand@admin.kth.se (Per Andersson) writes:
>>>I just can't remember how to switch on emacs editing in ksh.
>>You don't.
>Yes, I do. I do have the emacs version, so that wasn't the problem.

Sorry about that; I made an unwarranted assumption - that you were using
the vi version.

>For others that might be in the same situation, 
>EDITOR=emacs;export EDITOR
>VISUAL=emacs;export VISUAL
>FCEDIT=emacs;export FCEDIT
>in your .profile does the trick. It's probably the FCEDIT that does the trick.
>Also if the shell is already started 'set -o emacs' turns it on immediatly.
>Thanks to everyone responding!

The VISUAL variable isn't necessary, but having the other two set
probably is. I seem to remember that the manpage says that it's EDITOR
that it looks at, but I think FCEDIT is needed, too. Note that the shell
looks at the last part of the variable value, and as long as it ends in
emacs, it's OK; my FCEDIT contains the full path name of the emacs
program.

-- 
Jay Maynard, EMT-P, K5ZC, PP-ASEL   | Never ascribe to malice that which can
jay@splut.conmicro.com       (eieio)| adequately be explained by stupidity.
"It's a hardware bug!" "It's a      +----------------------------------------
software bug!" "It's two...two...two bugs in one!" - _Engineer's Rap_