Re: Configure a "widows" key on a 102-key keyboard
Hello,
On 4/24/25 01:24, 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.
>
>> Cheers,
>> David.
>>
>
AFAIK, the tool xmodmap doesn't work on Wayland. But with a little
search in the Internet there also exists similar tools.
As workaround you could also define the shortcut for open the
application launcher (KDE menu) within the KDE settings:
Settings->Shortcuts->Plasma->Activate Application Launcher Widget
On my system (running Debian 12) there was ALT-F1 predefined for
opening the KDE menu.
Kind regards,
Johannes
Reply to: