<div dir="ltr">On Wed, Mar 20, 2013 at 10:57 AM, Thomas Løcke <span dir="ltr"><<a href="mailto:thomas.granvej6@gmail.com" target="_blank">thomas.granvej6@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr"><div class="im">I'm not saying this is an xmonad issue as such, I'm saying that when I'm using xmonad, weird stuff happens when I use xmodmap to clear my numlock key. The same weird stuff does not happen when I use KDE or Fluxbox. These two WM's happily accept my .Xmodmap file and numlock stays disabled without other keyboard shortcuts being affected.</div>
</div></blockquote><div><br></div><div>They appear to be using different ways to intercept keys. xmonad is minimalist, and deliberately avoiding the higher level mechanisms in favor of simple passive grabs... but that means we rely on the X server doing the right thing with the keys at a low level, and if you try to use xmodmap to modify things hardcoded into Xkb's config this breaks.</div>
<div><br></div><div>(Actually, I would not be too surprised if they're trapping things at an even lower level which would let them avoid this, but that would be a lot of additional complex code. It's not too surprising that KDE at least might do so, since it also lets them avoid some differences in behavior with non-X11 interfaces [KDE has limited Windows support and somewhat buggy but functional native OS X support]. I have not studied fluxbox's code, but it may also be doing this. I can say that I would not particularly want to trap raw keycode events and implement the modifiers myself, as would be necessary with this approach; but it would at least partially avoid the X server getting confused about the modifiers because of Xkb/xmodmap conflicts.)</div>
<div><br></div><div>As for Xkb wizards, there are few such. Not even the xorg devs really understand it that well! See <a href="http://www.charvolant.org/~doug/xkb/html/index.html">http://www.charvolant.org/~doug/xkb/html/index.html</a> (although it seems to not be responding for me right now). It's a bit of a crawling horror, which nobody really understands (else they would have sorted out this mess, since they've known about it for something like ten years) and everyone is afraid to touch. That said, the basic solution is to use that web page as a guide, copy the Xkb keymap definition you're using and remove all the numlock-related parts. (Unfortunately, that may be easier said than done, given the mess that is Xkb.)</div>
<div><br></div></div>-- <br><div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net" target="_blank">ballbery@sinenomine.net</a></div>
<div>unix, openafs, kerberos, infrastructure, xmonad <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div>
</div>