help-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

super and hyper keys acting funny in emacs


From: J. David Boyd
Subject: super and hyper keys acting funny in emacs
Date: Fri, 21 Jun 2013 16:31:10 -0400
User-agent: Gnus/5.1299999999999999 (Gnus v5.13) Emacs/24.3 (cygwin)

I'm running the latest 32 bit cygwin under windows 7, and having a funny
problem with my hyper and super keys when I run emacs.


I've got my xserver configured to set the windows keys on the keyboard to be
super, and the caps lock to by hyper.


The output from 'setxkbmap -print' is:

xkb_keymap {
        xkb_keycodes  { include "xfree86+aliases(qwerty)"       };
        xkb_types     { include "complete"      };
        xkb_compat    { include "complete"      };
        xkb_symbols   { include 
"pc+us+inet(pc105)+altwin(alt_super_win)+capslock(hyper)"       };
        xkb_geometry  { include "pc(pc105)"     };
};

and if I run XEV, and press capslock I get:

KeyPress event, serial 32, synthetic NO, window 0xc00001,
    root 0x131, subw 0x0, time 8145997, (504,324), root:(2162,400),
    state 0x0, keycode 66 (keysym 0xffed, Hyper_L), same_screen YES,
    XLookupString gives 0 bytes: 
    XmbLookupString gives 0 bytes: 
    XFilterEvent returns: False

KeyRelease event, serial 32, synthetic NO, window 0xc00001,
    root 0x131, subw 0x0, time 8146122, (504,324), root:(2162,400),
    state 0x40, keycode 66 (keysym 0xffed, Hyper_L), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False


and if I press Left Windows key I get:

KeyPress event, serial 32, synthetic NO, window 0xc00001,
    root 0x131, subw 0x0, time 8148993, (504,324), root:(2162,400),
    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 32, synthetic NO, window 0xc00001,
    root 0x131, subw 0x0, time 8149102, (504,324), root:(2162,400),
    state 0x40, keycode 115 (keysym 0xffeb, Super_L), same_screen YES,
    XLookupString gives 0 bytes: 
    XFilterEvent returns: False



All perfect so far.  When I'm in a terminal, my keys look fine.

So, then I start up 'emacs -Q', and press C-h k, then, for example, Capslock-d,
(hyper-d) I get 'H-d is undefined'. Yeah!

Then I press C-h k, then Left-Win-d, (super-d), and I get 'H-d is undefined',
not 's-d is undefined', which is what I expected to see.

I've glanced through the src for emacs in what seems to be the pertinent
functions, but nothing jumps up at me that would cause emacs to combine the
setting for the Windows and CapsLock keys to be both be what CapsLock is set to.

Any ideas how I might resolve this?

Dave





reply via email to

[Prev in Thread] Current Thread [Next in Thread]