Shawn Betts <sabe...@gmail.com> writes: >> 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. > > Stumpwm doesn't use xkb. afaik there's no xkb extension available for > lisp. xkb is huge and complicated so reimplementing it in stumpwm > really isn't a good use of resources. But in this case, it should be > just a matter of figuring out how xkb interprets the keys and doing > the same thing. > > I think the long term solution is to implement the xkb extension in > clx and use that. No idea how involved that is.
In case anyone has some time: not desperately involved, but would take some work. There are two main pieces of work, if I remember right from the last time I looked at this: coming up with a nice enough lisp API for the protocol requests that should be exposed to client code, and (harder) hooking in the "right thing" behaviour for things that should "just work" without changing client code. This latter is harder mostly because clx as it currently stands doesn't have a desperately good way of dealing with extensions that need to modify the behaviour of the normal functions. It shouldn't be too hard, though; if anyone's interested, let me know and I'll try to help. Cheers, Christophe _______________________________________________ Stumpwm-devel mailing list Stumpwm-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/stumpwm-devel