Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!columbia!rutgers!husc6!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.unix.questions
Subject: Re: vms vs unix (actually, command-editing shells)
Message-ID: <5880@brl-smoke.ARPA>
Date: Fri, 22-May-87 19:00:11 EDT
Article-I.D.: brl-smok.5880
Posted: Fri May 22 19:00:11 1987
Date-Received: Tue, 26-May-87 02:20:43 EDT
References: <7494@brl-adm.ARPA> <12970@teknowledge-vaxc.ARPA> <19489@sun.uucp>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 11

In article <19489@sun.uucp> guy%gorodish@Sun.COM (Guy Harris) writes:
>> It uses arrow keys to move fore/backwards in the history list, and is
>> not tied to vt100s.
>Unfortunately, those two don't go together, unless you have "ksh"
>figure out from a "termcap" or "terminfo" entry what the arrow keys
>are.

Our solution for this is to allow the user to set his key bindings.
This can be done on a per-shell invocation basis if desired.  I used
this technique back when I was using a VT100 to assign all the keypad
escape sequences to editing functions (it took two levels of mapping).