Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!ucbvax!bloom-beacon!LARRY.MCRCIM.MCGILL.EDU!mouse
From: mouse@LARRY.MCRCIM.MCGILL.EDU (der Mouse)
Newsgroups: comp.windows.x
Subject: (none)
Message-ID: <8909130712.AA29892@Larry.McRCIM.McGill.EDU>
Date: 13 Sep 89 07:12:52 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 33

mouse@larry.mcrcim.mcgill.edu:

>> 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.

> 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.

Who are you to tell me I don't want just that?  (Generic "you", not
anyone specific.)  It's entirely plausible - in fact, often true - that
I *do* want some key to uniformly send a whole string (ie, not
something that can be done by changing the keycode-to-keysym mapping).

Maybe you want F4 to send one thing in xterm and another thing in
gnu-emacs; fine, that should be provided for.  But I want it to send
the same thing everywhere, and my point is that that should be provided
for as well, and it isn't.  Or rather, it is, but only when the string
is one character long (ie, when the situation can be handled by
reassigning keysyms).

As a simple example, suppose I have a key labeled "00" and I want it to
do what its label implies: generate two zero characters when typed.  I
don't see a keysym for that.  Or suppose I don't have such a key but I
want to pretend I have one (somewhat more plausible).

					der Mouse

			old: mcgill-vision!mouse
			new: mouse@larry.mcrcim.mcgill.edu