Michael Raskin <38a93...@rambler.ru> writes: >>> Here is what I put in .xsession: >>> >>> xmodmap -e "keycode 133 = grave" >>> xmodmap -e "keycode 75 = grave" >>Again, xmodmap just reshuffles what codes are sent, you can think of it >>(as far as stumpwm is concerned) as physically re-wiring the keyboard. >>If F9 sends a 'grave' keycode, stumpwm will think you pressed the prefix >>key (as you instructed it to :)) > > If sanity is worth nothing to someone, mapping F9 to backtick _after_ > StumpWM is loaded could work. StumpWM seems to grab a set of keycodes, > so if they are rewired after StumpWM has found out what the mapping is, > you can enter the grave character withut StumpWM minding.
I found that switching keyboard layouts (between qwerty and colemak) using the "group toggle" function of setxkbmap confused Stump a little: it thought the prefix "t" was on the same key no matter what layout I was using. I wonder if that's caused by the same issue: that it only reads keycodes once on startup? I don't suppose you know where in the code this happens? > Alternatively, you could remap the grave key to something really weird > and make this weird thing a prefix, then remap F9 to be grave character. > This is a saner way. > >>> 133 is the key code for the windows key on my keyboards. 75 is F9. >>> >>> Here is what I put in .stumpwmrc >>> >>> (set-prefix-key (stumpwm:kbd "`")) _______________________________________________ Stumpwm-devel mailing list Stumpwm-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/stumpwm-devel
