[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [STUMP] Strange keyboard layouts and Stumpwm

From: Shawn Betts
Subject: Re: [STUMP] Strange keyboard layouts and Stumpwm
Date: Thu, 17 Jun 2010 08:21:48 -0700

>> xmodmap -pk|grep -i level3
>     92         0xfe03 (ISO_Level3_Shift)       0x0000 (NoSymbol)
>     0xfe03 (ISO_Level3_Shift)
>    108         0xfe03 (ISO_Level3_Shift)       0x0000 (NoSymbol)
>    0xfe03 (ISO_Level3_Shift)

> mod5        ISO_Level3_Shift (0x5c),  Mode_switch (0xcb)

> AltGr:

The code that figures out what MOD altgr is on is broken. It's written
really stupidly :). As a short term fix, I suspect if you add keycode
108 to your mod5 list then it'll work.

The reason is because stumpwm uses a buggy xlib function that only
returns one keycode when asked to translate a keysym to a keycode. In
your case you have 2 keycodes mapped to the iso_level3_shift keysym
but only one of those keycodes is on mod5. Stumpwm says "xlib give me
all keycodes that map to iso_level3_shift!" xlib gives it the 108
keycode and not the 92 code because it's buggy. Then stumpwm looks in
the list of keycodes on mod5 asking "are any of the keycodes that map
to iso_level3_shift on mod5?" since it thinks 108 is the only
iso_level3_shift keycode the answer is no, causing it to fail to find
an altgr modifier.

What it SHOULD do is map all the keycodes on mod5 to keysyms and then
ask "are any of them iso_level3_shift?" if the answer is yes then
that's our altgr modifier. If anyone's up to the task, go for it. the
function is get-modifier-map. If not I'll try to fix it in the next
week or so.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]