Path: utzoo!attcan!utgpu!watmath!att!dptg!rutgers!cs.utexas.edu!uunet!cimshop!davidm
From: davidm@cimshop.UUCP (David Masterson)
Newsgroups: comp.emacs
Subject: Re: Function Keys in MG2a
Summary: XKEYS not working???
Keywords: MG FKEYS
Message-ID: <472@cimshop.UUCP>
Date: 21 Sep 89 18:13:30 GMT
References: <467@cimshop.UUCP> <18622@ut-emx.UUCP>
Organization: Consilium Mt. View CA
Lines: 44

In article <18622@ut-emx.UUCP> mic@ut-emx.UUCP (Mic Kaczmarczik) writes:
>In article <467@cimshop.UUCP> davidm@cimshop.UUCP (David Masterson) writes:
>> [ questions about MG2a startup ]
>
>You need to compile MG 2a with XKEYS defined.  After that, MG will
>look for a file called .mg-TERM, where TERM is the value of the
>logical name TERM (e.g. .mg-vt100 for a vt100 terminal type). If
>found, it will read and evaluate that file just like .mg.  This allows
>you to have different function key setups for different terminals,
>albeit in a slightly different manner than GNU Emacs does.
>
>---------------------------------------------------------------------
>;
>; Example key definition file for VT100 terminals using the termcap
>; driver. This only works if XKEYS is defined during compilation.
>;
>(global-set-key "\eOA" 'previous-line)	; up arrow
>(global-set-key "\eOB" 'next-line)	; down arrow
>(global-set-key "\eOC" 'forward-char)	; right arrow
>(global-set-key "\eOD" 'backward-char)	; left arrow
>------------------------------------------------------------------------ 

According to make.com in [.sys.vms], my MG is compiled with XKEYS on.  I tried
your .mg-vt100 file above and got mixed results.  Without the .mg-vt100 file,
none of the arrow keys worked with MG beeping at the ESC-O and inserting the
following character.  With the above .mg-vt100 file, the up and down arrows
seemed to work as specified, but the left and right arrows just beeped at me
(no inserted characters!) and a QUIT signal in the minibuffer.  I also added
(after the above):

(global-set-key "\e[6~" 'scroll-up) ; next screen
(global-set-key "\e[5~" 'scroll-down) ; previous screen

as a separate test (just to see how far things went) and they didn't take
either.  It seemed the "\e[" was recognized as backward paragraph and the "6~"
or "5~" were self-inserted (no QUIT signal).  Suggestions where to try
next? (help).

David Masterson
uunet!cimshop!davidm

p.s.  This is a VMS system running DECWindows and I am in a DECterm in VT300
mode.  The function keys do map to the above key sequences (checked with a ^Q
in MG), but I don't know if this is a timing thing.