On Tue, 26 May 2009 14:50:09 +0100
x...@coreland.ath.cx mentioned:
Hello.
I'm having a very strange problem with regards to the Mod4 key.
Currently, it's mapped to the windows key:
$ xmodmap -pm
xmodmap: up to 3 keys per modifier, (keycodes in parentheses):
shift Shift_L (0x32), Shift_R (0x3e)
lockCaps_Lock (0x42)
control Control_L (0x25), Control_R (0x6d)
mod1Alt_L (0x40), Alt_R (0x71), Meta_L (0x9c)
mod2Num_Lock (0x4d)
mod3
mod4Super_L (0x7f), Hyper_L (0x80)
mod5Mode_switch (0x5d), ISO_Level3_Shift (0x7c)
~/.xmodmaprc:
keycode 115 = Super_L
keycode 116 = Super_R
add Mod4 = Super_L
add Mod4 = Super_R
Unfortunately, I can't seem to get any wm to listen to Mod4. I can
use the following in ~/.fluxbox/keys, for example:
Mod4 Right :NextWorkspace
Mod4 Left :PrevWorkspace
...pressing Mod4 + left or Mod4 + right does nothing. No key setting
involving Mod4 does anything.
xev shows the key event occuring (in other words, if I hold 'T',
for example, and then tap the windows key, a few of the fields change
for the 'T' key event - suggesting a modifier key is being pressed).
Any ideas?
Are you sure that windows keys really get mapped to Super_XXX keys?
What modifier does xev show?
--
Stanislav Sedov
ST4096-RIPE
pgpqYKqrEFx4u.pgp
Description: PGP signature
!DSPAM:4a265e5e994291756313629!___
xorg mailing list
xorg@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/xorg
