You are not logged in.

#1 2013-03-19 09:42:38

girzel
Member
Registered: 2010-06-27
Posts: 74

setxkbmap oddness

I'm a little doubtful that this is the right forum for this question, but at the very least I'm hoping someone will point me in the right direction. First of all, I should say that my problem may be connected to this one:

https://bbs.archlinux.org/viewtopic.php?id=157905

I'm using bare Stumpwm as my window manager (no desktop environment), with the default "Ctrl-t" as the prefix key: all (anyway most) Stumpwm commands start with that. At the same time, I'm trying to switch to colemak as a keyboard layout, to prevent qwerty from breaking my fingers. I find that if I set colemak as my keyboard layout using an "absolute" statement:

$ setxkbmap us -variant colemak

It works as expected: Stumpwm's prefix key tracks the new location of "t", which is where "f" is on a qwerty layout. All is correct. But if I use grouping like so:

setxkbmap -option 'grp:shifts_toggle' -variant ',colemak' -layout 'us,us'

Which is what I really want, then after I've shifted to colemaks using the shifts toggle, Stumpwm reads its prefix key incorectly. For the first keystroke, I have to hit the actual "Ctrl-t" key, as it appears on my qwerty keyboard -- ie, "t" is still read as "t", even though the keyboard should be sending a "g" under Colemaks. Only the first key is read incorrectly. If I want to send "Ctrl-t Ctrl-t" to Stumpwm, I have to press "Ctrl-t Ctrl-f": the first "t" is read according to the qwerty keyboard, the second according to the colemaks keyboard.

I've raised this on the Stumpwm mailing list to no response. I don't know if it's a Stumpwm problem or a XKB problem, and if it's the latter, I don't know where to raise it. Someone point me in the right direction, please!

Eric

Offline

Board footer

Powered by FluxBB