pbrad at cinci.rr.com
Fri Aug 9 04:15:51 BST 2002
Here is what I get when I run xev and then I click the "windows" key:
KeyRelease event, serial 27, synthetic NO, window 0x2200001,
root 0x37, subw 0x0, time 2365491217, (185,316), root:(189,361),
state 0x40, keycode 115 (keysym 0xffeb, Super_L), same_screen YES,
XLookupString gives 0 characters: ""
I tried doing this to get the map to work, but you see I get an error:
[root at toybox bpotts]# xmodmap keycode 115=F29
xmodmap: unable to open file 'keycode' for reading
xmodmap: unable to open file '115=F29' for reading
xmodmap: 2 errors encountered, aborting.
Am I doing this wrong? I read the instructions a few times thinking I was
missing something, but I'm seeming to have trouble with this.....
Any other suggestions?
Thanks in advance,
On Thursday 08 August 2002 12:54 pm, you wrote:
> Two stages. First, you have to use xmodmap to map the Windows key to
> something recognizable. The following may work, but if not, just use "xev"
> to see what key event that key sends.
> What I have pasted in here is my entire xmodmap. You are only really
> interested in the
> keycode 117 = F29
This message is from the kde mailing list.
Account management: http://mail.kde.org/mailman/listinfo/kde.
More info: http://www.kde.org/faq.html.
More information about the kde