On Sun, Mar 06, 2011 at 02:57:56AM +0100, Cyril Brulebois wrote:
> >
> > with the same version…
> >
> > > I use the following line:
> > >
> > > setxkbmap -layout "us,gr(polytonic)" -model "pc104" -option
> > > terminate:ctrl_alt_bksp -option caps:super -option grp:alt_shift_toggle
> > > -option grp_led:caps -option compose:menu -option altwin:hyper_win
> >
> > that seems to work for me, pressing the windows key gives me Hyper_L.
> >
> > What's the output of setxkbmap -print?
11/04/2011, 22:41:31 azure@electric:~% setxkbmap -print
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete+ledcaps(group_lock)" };
xkb_symbols { include
"pc+us+gr(polytonic):2+inet(evdev)+altwin(hyper_win)+group(alt_shift_toggle)+capslock(super)+compose(menu)+terminate(ctrl_alt_bksp)"
};
xkb_geometry { include "pc(pc104)" };
};
> > > All options are effective except for altwin:hyper_win. Both windows
> > > keys continue to act as Super modifiers.
> >
> > How do you check that? Try xev?
Ah, I see now that my problem is not actually in xkb but in my
applications. xev says that my windows keys actually are hyper. I
had thought XKB was not working because Emacs identified Windows-A as Super A.
My apologies for the spurious bug. I shall look into how to make
Emacs behave properly.
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110412025344.ga5...@azureprime.com
