davidm@uunet.UU.NET (David S. Masterson) (01/13/91)
>>>>> On 4 Jan 91 17:55:40 GMT, meb4593@galileo.rtn.ca.boeing.com (Michael Bain) said:
Michael> We have successfully (?) compiled microemacs 3.10 on several VAXen
Michael> (running VMS), however the arrow and function keys do not respond.
Michael> Control and Meta sequences work fine. We tried setting the Keypad
Michael> Application mode as suggested in the manual.
I'm running MicroEmacs 3.9e on VMS, but, I assume, there isn't much of a
difference in this case. Application keypad mode on VT100 style keyboards
applies to the numeric "keypad" on the right side ONLY. The function and
arrow keys are not controlled by that setting (I think -- I'm more used to
Unix myself). Even so, both the terminal (via its internal setup) and VMS
(via SET TERMINAL) should be set to Application Keypad Mode so that the keypad
generates escape codes for each key so Emacs can differentiate them from the
numbers at the top of the keyboard.
Do the function keys and arrow keys respond at all? That is, when you hit an
arrow key, does anything show up in the emacs buffer? If your keys are not
responding at all, then its probably a terminal/VMS setting that I can't help
with. If they are responding, try typing ^Q (quote-character) and then hit
the same arrow key. You should see something like '^[[B' appear in your
buffer which means Emacs is seeing your keys as a sequence of keys (ESC[B).
Do this with all your function/arrow keys so that you have essentially a
translation of each function key into the key sequences that Emacs sees it as.
My understanding of 3.10 is that the function key translation methodology has
changed from 3.9. Check your manual closely to see if it addresses this. If
it can't offer ideas, then you may have to go into the source code. The
question is how uEmacs handles extended key sequences.
In version 3.9e, I had to make changes to INPUT.C in the functions getcmd()
and get1key(). When the getcmd() function recognized the incoming key as an
ESC, it would begin looking for the next key to see what type of META command
it was. In this processing, if the next character was either '[' or 'O' (not
zero), then it assumed it was an extended key sequence and processed it as a
SPECial key. This last bit of processing needed to be extended for the
function keys (which had the form 'ESC[' followed by 1-3 numbers and ending in
'~'). The important point, though, is that the processing was already there
to handle the arrow keys, I just needed to extend it for the VT100 function
keys.
This ought to get you started. Good luck.
--
====================================================================
David Masterson Consilium, Inc.
(415) 691-6311 640 Clyde Ct.
uunet!cimshop!davidm Mtn. View, CA 94043
====================================================================
"If someone thinks they know what I said, then I didn't say it!"