Subject: Re: command-line editing and "standard" shells....
To: Jason Thorpe <thorpej@nas.nasa.gov>
From: Chris Jones <cjones@rupert.honors.montana.edu>
List: current-users
Date: 03/18/1999 17:30:05
>>>>> "Jason" == Jason Thorpe <thorpej@nas.nasa.gov> writes:
Jason> On Thu, 18 Mar 1999 18:19:17 -0500 (EST) woods@most.weird.com
Jason> (Greg A. Woods) wrote:
>> /bin/sh and /bin/ksh both support cursor keys. Once you enable
>> command-line editing, cursor keys work. PD-ksh currently has the
>> advantage because setting 'EDITOR' and/or 'VISUAL' to some string
>> that stars with either "vi" or "emacs" will automatically select
>> and enable the desired command-line editing mode.
Jason> Yah, I have to override this, personally. I'm a die-hard vi
Jason> weenie, but I like ksh to use emacs key bindings :-)
I had the same objection, until I fired up ksh on my NetBSD/alpha
box. Using my .shrc, everything works fine: I have "EDITOR=vi" and
"set -o emacs" in there, and it gives me emacs keybindings for history
editing. Hitting ESC twice in a row gets file completion. I may have
to switch shells now...
Chris
--
-----------------------------------------------------cjones@math.montana.edu
Chris Jones cjones@honors.montana.edu
Mad scientist at large cjones@nervana.montana.edu
"Is this going to be a stand-up programming session, sir, or another bug hunt?"