🚀 go-pugleaf

>	You can also place "map" commands in your .exrc file (or EXINIT
>	environment variable), where they will be automagically executed
>	every time you invoke ex or vi. You don't need actual ^V escapes
>	in .exrc (although you'll need ^V to put the necessary control
>	characters into the file in the first place).

If you put map commands in your .exrc file, and the map commands contain
control characters, make sure the beautify option (bf) isn't set until
*after* the map commands; otherwise, the control characters will be
stripped out of the map commands. 

--
Scott Stevens
AT&T Consumer Products Laboratories
Indianapolis, Indiana
UUCP: inuxh!stevens

Someone mentioned that the HP 2621 function keys locked up his terminal.
Same thing happened to me (on my 2623) until I changed some configuration
bits.  In particular, (at least on my '23) there are two datacomm
configuration bits called Inhibit Handshake and Inhibit DC2 which
control block-mode transfer protocols.  These default to NO (softkey menu
configurable on the '23) for HP computers (which have some weird
terminal handshaking).  For most other machines, set them to YES
and no handshaking is done; the function keys' codes are simply sent,
no questions asked.

As for actually using these keys, the map suggestion for vi is about
the best I've heard.  (Unless you can create shell scripts with names
like <ESC>v - maybe that would work in the shell.)
All the more recent versions (2622 on) have real softkeys: you
can program the contents (what is sent to the computer) as well as the label.