arnuld uttre <arnuld.miz...@gmail.com> writes: >> 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.
What happens if you enter it in a xterm? What does xmodmap print then? The correct place for the line should be your .xinitrc, .Xsession or whatever is loaded when your X session starts (IIRC gdm loads .xsessionrc). Regards, olli -- Oliver Heins o...@sopos.org F27A BA8C 1CFB B905 65A8 http://www.sopos.org/olli/ 2544 0F07 B675 9A00 D827 1024D/9A00D827 2004-09-24 -- gpg --recv-keys 0x9A00D827 Please avoid sending me Word or PowerPoint attachments: http://www.gnu.org/philosophy/no-word-attachments.html
