Re: Configure a "widows" key on a 102-key keyboard
On Wed 23 Apr 2025 at 16:24:24 (-0700), Van Snyder wrote:
> On Wed, 2025-04-23 at 17:04 -0500, David Wright wrote:
> > On Wed 23 Apr 2025 at 13:52:07 (-0700), Van Snyder wrote:
> > > On Wed, 2025-04-23 at 14:26 -0500, David Wright wrote:
> > > >
> > > > XKBOPTIONS="lv3:ralt_switch,compose:caps,terminate:ctrl_alt_bksp"
> > >
> > > xev says the Windows key is known to X as "Menu."
> > >
> > > XKBOPTIONS="pause:menu"
> > >
> > > didn't work.
> > >
> > > Yes, I did reboot after editing /etc/default/keyboard.
> >
> > You might try using xmodmap to set it: the man page has several
> > examples. You would then put the command into, say, ~/.xsession
> > so that it gets run automatically at startup.
>
> xev said "pause" is 127, so I used xmodmap to set 127 to Menu:
>
> xmodmap -e "keycode 127 = Menu"
>
> xev than said the "pause" key is "Menu." But it didn't raise the KDE
> menu the way the Window key does, even though xev also says the
> "Window" key is "Menu"
>
> I also put
>
> xmodmap -e "keycode 127 = Menu"
>
> into .xsession, made it executable, linked it to .Xsession, and put
>
> keycode 127 = Menu
>
> into ~/.Xmodmap
>
> and when I rebooted, xev said "Pause" is "Menu" but it doesn't start
> the KDE menu.
>
> Maybe KDE subverts X11 settings.
In that case, I would try something simpler, in order to ascertain
where the problem lies. Eg, if you replace "Menu" by "slash", does
the Pause key print / ? Straightaway? After logout/in? After reboot?
I don't know when or whether KDE or *dm reads .xsession or Xsession,
but DEs tend to be complicated in how they start up. The subject
often crops up here and bemuses me. You'll have to figure that out.
Once you get a Pause substitution to work, then you can start testing
what Menu is meant to do in whichever DE you use. I don't define Menu
in my Window Manager, but I can test it works in FireFox. It has the
same effect as pressing the righthand mouse button (except for where
the Menu pops up; IOW, not stuck to the mouse pointer).
Cheers,
David.
Reply to: