aperez@cvbnet2.UUCP (Arturo Perez Ext.) (09/02/88)
From article <8808251921.AA13762@godzilla.ele.toronto.edu>, by moraes@godzilla.ele.toronto.EDU (Mark Moraes):
It seems that the default X key mappings for Sun workstations
aren't exactly "out-of-the-box" useable. So I created a
keymap file to emulate the function key mappings used for
the SUNTOOLS vt100tool. Now I can use the same keystokes
and I no longer need to scratch my head wondering what key
to press to get EDT to respond.
The bug part comes in like so. After writing the keymap
file and feeding it to xmodmap, I tried out the new mappings.
However, none of my existing windows got the changed map. But
any newly created windows did. I perused the documentation.
In the manual for xmodmap it says
Every time a keycode expression is evaluated, the server
generates a MappingNotify event on every client. ...
... Clients that receive keyboard
input and ignore MappingNotify events will not notice any
changes made to keyboard mappings.
Does this mean that xterm should be watching for MappingNotify?
Or are changes in the keymapping envisioned to be so rare as
to not require extra ordinary vigilance on the part of applications?
And, lastly, should xterm be changed?
Arturo Perez
ComputerVision, a division of Prime
primerd!cvbnet!aperez
The difference between genius and idiocy is that genius has its limits.RWS@ZERMATT.LCS.MIT.EDU (Robert Scheifler) (09/07/88)
Date: 1 Sep 88 21:11:27 GMT
From: linus!raybed2!cvbnet2!aperez@husc6.harvard.edu (Arturo Perez Ext.)
Does this mean that xterm should be watching for MappingNotify?
Yes.
Or are changes in the keymapping envisioned to be so rare as
to not require extra ordinary vigilance on the part of applications?
No, applications should handle this. The (new) Intrinsics will do this
for applications automatically.