Shawn Betts <sabe...@gmail.com> writes: > 2010/6/17 Eric Wolf <e...@boese-wolf.eu>: >> Shawn Betts <sabe...@gmail.com> writes: >> >>> 2010/6/17 Eric Wolf <e...@boese-wolf.eu>: >>>> Shawn Betts <sabe...@gmail.com> writes: >>>> >>>>>> still the same problem >>>>> >>>>> What's the output from the 'modifiers' command? >>>> >>>> Sorry, forgot that. >>>> >>>> Meta: mod-1 >>>> Alt: >>>> Super: mod-4 >>>> Hyper: >>>> AltGr: mod-5 >>> >>> At least it recognizes where altgr is supposed to be. I have a >>> different layout than you but when I configure altgr stumpwm >>> recognizes the altgr keys. So something I'd like to look at is the >>> entire output of 'xmodmap -pk' to see if the keycode mapping is not >>> what I'm expecting it to be. Can you send me that? >> >> Of course >> >> Might look strange, its a special ergonomic layout called neo2. > >> 29 0x006b (k) 0x004b (K) 0x006b (k) 0x004b (K) >> 0x0021 (exclam) 0x07ea (Greek_kappa) 0x00a1 (exclamdown) 0x0000 >> (NoSymbol) 0x00d7 (multiply) > > Looks like it's behaving properly. ISO_Level3_Shift tells the app to > grab the 3rd index in the keycode mapping, which is k. Presumably > ISO_Level5_Shift tells it to grab the 5th index, which is !. > Unfortunately, stumpwm doesn't handle ISO_Level5_Shift, but it easily > could. > > Is there a name for the level5 shift key? AltGr2 or something? :)
What about “Level5”? But I don't know if there is some widely accepted name. But there are a few things I don't understand. I looked on my xmodmap -pk output to check wether the line above is truly correct and yes it is! But whats a little bit annoying about that is, that I get my ! with ISO_Level3_Shift + k. So I thought it must come from the differences in xkb and xmodmap. The Keyboard layout comes as three files for xkb. So I downloaded the alternative xmodmap-driver for a user install and tried that. You can get it at http://neo-layout.org/neo_de.xmodmap and load it with setxkbmap lv && xmodmap neo_de.xmodmap. (setxkbmap lv is needed to get X to eval the higher levels over the b for example.) and now I have the following output: xmodmap: ------------------------------------------------------------------------------ shift Shift_L (0x32), Shift_R (0x3e) lock Mode_switch (0x42) control Control_L (0x25), Control_R (0x69) mod1 Alt_L (0x40), Meta_L (0xcd) mod2 Tab (0x4d) mod3 mod4 Super_L (0x85), Super_R (0x86), Super_L (0xce), Hyper_L (0xcf) mod5 ISO_Level3_Shift (0x5c), Mode_switch (0xcb) xmodmap -pk | egrep '^[[:space:]]+29' ------------------------------------------------------------------------------ 29 0x006b (k) 0x004b (K) 0x0021 (exclam) 0x07ea (Greek_kappa)0x00a1 (exclamdown) 0x0000 (NoSymbol) 0x00d7 (multiply) StumpWM modifiers command ------------------------------------------------------------------------------ Meta: mod-1 Alt: Super: mod-4 Hyper: AltGr: mod-5 AND STILL C-t <caps>+k kills windows instead of an exec. Another thing is disturbing me: Does StumpWM use the xkb extension, if not there might be a problem with the xkb-version of neo, but why does the xmodmap-version not work? Now ! should be on mode_switch+k, where xev and emacs can find it, but C-t + <caps>-k doesn't work as expected. I'm not an expert in this field and I have trouble finding documentation for xkb and xmodmap, so I don't know how I can help. I would be glad, if could use my favorite WM with my favorite keyboard layout. Yours sincerely, Eric _______________________________________________ Stumpwm-devel mailing list Stumpwm-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/stumpwm-devel
