esteffl_at_pbi.net <esteffl_at_pbi.net> wrote:
>
> thanks a lot for clarification. that means that the exceed server is
> broken, right? (since the numlock does not have any effect on shortcuts)
No, it just means that the default modifier of Num_Lock is different
than it is for your Unix server. If you run "xmodmap -pm" you will see
what modifiers are defined to be what. Different X servers can have
different defaults.
Here's my HPUX server:
$ xmodmap -pm
xmodmap: up to 2 keys per modifier, (keycodes in parentheses):
shift Shift_R (0xd), Shift_L (0x18)
lock Caps_Lock (0x1c)
control Control_R (0xe), Control_L (0x19)
mod1 Alt_R (0xf), Alt_L (0x12)
mod2
mod3
mod4
mod5
And here's my Linux server:
$ xmodmap -pm
xmodmap: up to 2 keys per modifier, (keycodes in parentheses):
shift Shift_L (0x32), Shift_R (0x3e)
lock Caps_Lock (0x42)
control Control_L (0x25), Control_R (0x6d)
mod1 Alt_L (0x40), Alt_R (0x71)
mod2 Num_Lock (0x4d)
mod3
mod4
mod5 Scroll_Lock (0x4e)
As you can see, the Linux (XFree) server defaults to adding a few
modifiers that HPUX does not. So under XFree, hitting Num-Lock or
Scroll-Lock by mistake, causes lots of keys to stop working. Under
HPUX, hitting Num-Lock has little effect.
If I really wanted to fix this behavior, I suppose a command like
"xmodmap -e 'Clear mod2' -e 'Clear mod5'" would do the trick.
--
fox_at_dallas.net (Fuzzy Fox) || "Just about every computer on the market
sometimes known as David DeSimone || today runs Unix, except the Mac (and
http://www.dallas.net/~fox/ || nobody cares about it). -- Bill Joy '85
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Wed Sep 01 1999 - 14:22:53 BST