Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!dciem!nrcaer!cognos!jimp
From: jimp@cognos.uucp (Jim Patterson)
Newsgroups: comp.sources.d,comp.emacs
Subject: Re: when using jove, get the keymap right!
Message-ID: <977@cognos.UUCP>
Date: Wed, 24-Jun-87 13:49:16 EDT
Article-I.D.: cognos.977
Posted: Wed Jun 24 13:49:16 1987
Date-Received: Fri, 26-Jun-87 03:16:18 EDT
References: <1283@cullvax.UUCP> <1183@osiris.UUCP> <320@xios.XIOS.UUCP>
Reply-To: jimp@cognos.UUCP (Jim Patterson)
Organization: Cognos Incorporated, Ottawa, Canada
Lines: 26
Xref: dciem comp.sources.d:785 comp.emacs:1014

In article <320@xios.XIOS.UUCP> greg@sdn.UUCP (Greg Franks) writes:
>I understand that jove can be made to understand function keys quite
>easily. 

We've done this, and while it's easy for some terminals, others
(notably VT-200 type terminals) need some reprogramming.  The
problem is that JOVE keymaps are oriented around prefix characters
into other keymaps. Since there are only 4 keymaps and some VT200
function keys have 5 characters (e.g. "^[[21~"), there's no way
to describe them using the prefix format. SUN workstations and
Dasher terminals (in ANSI mode) are even worse; they always generate
six character sequences.

What we've done is to decode the function number (21 in the example
above) and use it as an index into one of the keymaps.  This works
fine, but may conflict with other uses of the keymap.  The function
keys should really have their own keymap or keymaps.  

If people are interested I can assemble diff listings to post (I
haven't seen much discussion about JOVE lately, even though we use it
a lot).

-- 

Jim Patterson          decvax!utzoo!dciem!nrcaer!cognos!jimp
Cognos Incorporated