Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10 5/3/83; site cbosgd.UUCP
Path: utzoo!linus!philabs!seismo!harpo!eagle!mhuxl!ihnp4!cbosgd!mark
From: mark@cbosgd.UUCP
Newsgroups: btl.general,net.followup
Subject: Re: HP2621P Function Keys
Message-ID: <742@cbosgd.UUCP>
Date: Fri, 16-Dec-83 15:13:07 EST
Article-I.D.: cbosgd.742
Posted: Fri Dec 16 15:13:07 1983
Date-Received: Sat, 17-Dec-83 08:01:18 EST
References: <438@ihuxs.UUCP>, <422@ihuxq.UUCP>
Organization: AT&T Bell Laboratories, Columbus
Lines: 20

It is preferred to use the function key notation, rather than putting
the particular escape sequences your 2621 sends into your .exrc.
That is, instead of
	map ^V^[q^V^M dd
use
	map #2 dd
(because the escape q cr key is F2).  This avoids putting escape
sequences in your file, and it also means your F2 key will work the
next time you use something other than a 2621.  Also, the beautify
problem mentioned earlier does not apply to the EXINIT environment
variable, which is preferred anyway because vi will start up faster.

By the way, if it's really vi you want to extend, it's usually easier
to load up some of the unused characters (yes, Virgina, there are a
few keys that don't do anything in vi) instead of depending on function
keys that are in different places, if at all, on your keyboard.
(Especially if you're a 2621 user and don't enjoy holding down shift
to make them work.)  I have permanent macros on my command mode ^O key
and my insert mode ^L key, and usually put temporary macros on my g,
v, and q keys, which are otherwise unused in normal command mode.