[xmonad] Further xmodmap and numlock woes

Thomas Løcke thomas.granvej6 at gmail.com
Tue Mar 19 15:46:58 CET 2013


On Tue, Mar 19, 2013 at 3:39 PM, Brandon Allbery <allbery.b at gmail.com>wrote:

>
> Data.Monoid has both.
>


Thanks! My xmonad.hs file now compiles without error, so YAY!

Did it work then?

Well, yes and no. It works if xmonad is already running, ie. I open a
terminal and enter xmodmap -e "clear mod2". The numlock key is now
disabled, so clicking it, even frantically, does nothing and my mod key is
still fully functional. It doesn't work if I add "clear mod2" to my
.Xmodmap file though and neither does it work if I call xmodmap -e "clear
mod2" from .xinitrc. xmonad starts up, the numlock key is disabled but my
xmonad mod key doesn't work.

So a couple of steps forward, and then one back.

Can something be done to Adam's original proposed solution, so it'll also
handle me clearing mod2 from either .Xmodmap or .xinitrc before xmonad is
started?




>
> No; some github worshipper took it on himself to fork xmonad onto github
> on the grounds that any project not on github is obviously dead and
> unmaintained and it was up to him to "save" it (this is very nearly word
> for word from the mailing list discussion!), but somehow nobody actually
> followed him along the path to salvation and it hasn't been updated since
> he did it. The official repo is still darcs at
> http://code.haskell.org/xmonad/ and http://code.haskell.org/XMonadContrib.
>



OK, good to know. Thanks.

:o)
Thomas Løcke
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/xmonad/attachments/20130319/e197a7e2/attachment.htm>


More information about the xmonad mailing list