Re: Can't bind Mod (windows logo) key in kb shortcuts
- From: Havoc Pennington <hp redhat com>
- To: Ben Davis <ben xsusio com>
- Cc: gnome-list gnome org
- Subject: Re: Can't bind Mod (windows logo) key in kb shortcuts
- Date: Sun May 11 02:51:01 2003
On Sun, May 11, 2003 at 01:35:04AM -0500, Ben Davis wrote:
> xmodmap: up to 2 keys per modifier, (keycodes in parentheses):
>
> shift Shift_L (0x32), Shift_R (0x3e)
> lock Caps_Lock (0x42)
> control Control_L (0x25), Control_R (0x6d)
> mod1 Alt_L (0x40), Alt_R (0x71)
> mod2 Num_Lock (0x4d)
> mod3
> mod4
> mod5
>
>
> Hmm... on my laptop (the one that works) it shows "mod4 Super_L
> (0x73), Super_R (0x74)"... Am I using the wrong kb driver or something?
You just don't have the windows key (typically set up as Super) bound
to any modifier. This is a keymap issue; sometimes when installing a
Linux distribution you need to choose 104-key or 105-key keyboard
instead of 101-key. Different distributions do it different ways.
Look for "XkbModel" in XF86Config I think.
Havoc
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]