Steve Youngs <steve@xxxxxxxx> writes:
> * Zajcev Evgeny <zevlg@xxxxxxxxx> writes:
>
> > Steve Youngs <steve@xxxxxxxx> writes:
> >> First of all, let me say that I _can_ use the left Hyper key as
> >> normal for almost all things. But...
> >>
> >> H-h k <Hyper_L> => ╪ runs `xwem-self-insert-or-undefined'
> >>
> >> H-h k <Hyper_R> g => H-g runs `xwem-keyboard-quit'
> >>
> >> I had a look in xev...
> >>
> >> Hyper_L:
> >>
> >> keysym - 0xffed keycode - 115
> >>
> >> Hyper_R:
> >>
> >> keysym - 0xffee keycode - 116
> >>
> >> $ xmodmap|grep Hyper RET
> >> mod4 Hyper_R (0x74), Hyper_L (0x80)
>
> > This thing looks like your Hyper_L is not modifier(despite xmodmap
> > report),
>
> And despite XWEM treating it as a modifier 99.9% of the time.
>
> > or xwem falsely treats Hyper_L as non-modifier for some
> > reason
>
> Only in some circumstances.
>
> > (xwem-kbd-kcode-modifier-p 115)
>
> nil
>
> Which is very odd, because I _can_ use Hyper_L as a modifier.
>
> > xwem-xmods-mapping
>
> ((50 62 0) (66 0 0) (37 109 0) (64 125 156) (77 0 0) (117 0 0) (116
> 128 0) (93 124 0))
Oh, hehe .. i just realized the problem:
Note xev reported you keycode 115(0x73) for Hyper_L, BUT xmodmap
reports 0x80(128!) as keycode for Hyper_L, so i think you have two
keycodes[physical keys (115 and 128)] which generates Hyper_L keysym
.. one of them is modifier and other is not!
Please do $ xmodmap -pk |grep Hyper to check this out ..
Also please note state of your NumLock lock modifier, i.e. maybe your
Hyper_L does not work only if numlock is on?
>
> > It also might be useful to report this as bug, with enabled
> > xwem-debug capacities.
>
> OK, will do so in a minute.
>
--
lg
|