> On Mon, Jun 15, 2009 at 8:25 PM, Oliver Heins<o...@sopos.org> wrote:
> As I had a similar issue recently, but with dwm:
>
> Which keycode does xev print when you press the Windows key? If it's
> not 127 (=0x7f) try something like this:
>From xev:
KeyPress event, serial 28, synthetic NO, window 0xa00001,
root 0x3f, subw 0xa00002, time 3882474306, (38,21), root:(39,408),
state 0x0, keycode 115 (keysym 0xffeb, Super_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False
KeyRelease event, serial 28, synthetic NO, window 0xa00001,
root 0x3f, subw 0xa00002, time 3882474407, (38,21), root:(39,408),
state 0x0, keycode 115 (keysym 0xffeb, Super_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False
> xmodmap -e "keycode 115 = Super_L"
>
> where 115 is the keycode xev prints.
>
> However, this might be a problem of wmii, so this is just a guess.
I added that line to ~/.bashrc but that does not seem to resolve the
issue. The I added that to ~/.wmii-hg/rc.wmii (just before last wmiir
event loop line) but that too does not work.
--
http://uttre.wordpress.com/2008/05/14/the-lost-love-of-mine/
