Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!apple!agate!helios.ee.lbl.gov!epb2.lbl.gov!envbvs
From: envbvs@epb2.lbl.gov (Brian V. Smith)
Newsgroups: comp.windows.x
Subject: Re: NumLock and similar keys
Message-ID: <3785@helios.ee.lbl.gov>
Date: 13 Sep 89 01:14:33 GMT
References: <8909122249.AA22882@Larry.McRCIM.McGill.EDU>
Sender: usenet@helios.ee.lbl.gov
Lines: 20

In article <8909122249.AA22882@Larry.McRCIM.McGill.EDU>,
mouse@LARRY.MCRCIM.MCGILL.EDU (der Mouse) writes:
<
< 
< I agree that XLookupString could use a lot of work.  For example, there
< is currently no way to arrange things so that a press on F4 gets turned
< into the string "foobar" (for example) uniformly.  Xterm can handle
< this, but setting up a translation in xterm isn't much help when you're
< typing to a gnu-emacs window.  Having to specify the same translation
< for each client is less than ideal, particularly when they aren't
< uniform in the way you specify it.

This is precisely what is supposed to happen.
The theory is that you want the F4 key (say) to send a different
string depending on whether you are in xterm or gnu-emacs.

_____________________________________
Brian V. Smith    (bvsmith@lbl.gov)
Lawrence Berkeley Laboratory
I don't speak for LBL, these non-opinions are all mine.