Re: Num_Lock under solaris 5.8

[Klaus Zeitler <kzeitler@lucent.com>]

>>>>> "Jan" == Jan Djärv <jan.h.d@swipnet.se> writes:
    Jan> 
    Jan> You can try to change Num_Lock to some other Mod.

I have also tried things like:
add Mod3 = Mode_switch
keycode 0x60 = KP_End KP_1 1 1
in my xmodmap file with the hope that pressing the Mode_switch key would 
give me keys 3 and 4, i.e "1" from the xmodmap definitions.
(This works fine for e.g. "keycode 0x0B = a A adiaeresis Adiaeresis"
but not for the keypad). xev (similar to the Num_Lock problem) says:
XLookupString gives 0 characters.

Besides (even more annoying) it looks as if every modifier that I try to
define as Mod3 becomes automatically sticky, that's why I gave up the idea
of redefining Mod3.

Rumor has it that we'll switch to Solaris 5.10 in a few months. Maybe
that'll help.

Thanks for your quick and detailed support.

Klaus

-- 
 ------------------------------------------
|  Klaus Zeitler      Lucent Technologies  |
|  Email:             kzeitler@lucent.com  |
 ------------------------------------------
---
Rule of Defactualization:
 Information deteriorates upward through bureaucracies.