At Tue, 30 Jun 2009 23:06:32 -0700, Shawn Betts wrote:
> > xmodmap -e 'keycode 133 = F20' -e 'clear Lock' -e 'keycode 66 = F19'
> >
> > But I never got my StumpWM prefix key back.
>
> Next time this happens, boot up xev, hit some keys, and look at what
> they're interpreted as. If the lock modifier is on in the key presses,
> then that's the problem.
A couple of days ago I did upgrade from Fedora 11 to development
branch and found that StumpWM doesn't recognize F20 (keycode 133) with
new X.org version (1.7-pre) anymore. I did such quick hack:
diff --git a/input.lisp b/input.lisp
index 932e990..d5a616d 100644
--- a/input.lisp
+++ b/input.lisp
@@ -574,7 +574,7 @@ input (pressing Return), nil otherwise."
mod1-codes
mod2-codes
mod3-codes
- mod4-codes
+ (remove-if (lambda (x) (eql x 133)) mod4-codes) ; hack for buggy X
in fc12
mod5-codes)))
(defun get-modifier-map ()
--
wbr, Vitaly
_______________________________________________
Stumpwm-devel mailing list
Stumpwm-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/stumpwm-devel
