Skip to content

Allow app launcher shortcuts while a menu is open - #14158

Closed
SeniorMatt wants to merge 2 commits into
linuxmint:masterfrom
SeniorMatt:launcher-shortcuts-in-menus
Closed

SeniorMatt wants to merge 2 commits into
linuxmint:masterfrom
SeniorMatt:launcher-shortcuts-in-menus

Conversation

@SeniorMatt

Copy link
Copy Markdown

With the menu open, Super+Shift+C (my terminal shortcut) did nothing and typed "C" into the search box instead.

  • keybindings: the built-in launcher keys (Home, Calculator, Search, Email, Help, Terminal, WWW) are allowed in POPUP mode, like custom keybindings already are. The menu closes first so the new window doesn't end up behind it.
  • st-entry: Super+letter no longer inserts text (ClutterText only skips Control). Input method events still go through.

Similar idea to #13952. Tested on Mint 27 (Wayland): the shortcuts work with the menu open, and typing and searching in the menu are unchanged.

With the menu open, pressing the Terminal shortcut (for example
Super+Shift+C) did nothing and a "C" appeared in the search entry
instead.

Custom keybindings are allowed in POPUP mode, but the built-in launcher
media keys (Home, Calculator, Search, Email, Help, Terminal, WWW) were
NORMAL only. While a menu holds the modal grab, Main._stageEventHandler
dropped them and passed the key on to whatever had key focus.

Allow the launchers in POPUP mode too. A launcher started this way
closes the menu first, so the new window doesn't open behind it. Do the
same for custom keybindings, which were already allowed but left the
menu open.
In an entry, Super+letter combinations that aren't bound to anything,
or whose binding isn't allowed in the current action mode, insert the
letter. With the menu open, Super+Shift+C typed "C" into the search
entry. ClutterText only skips keys pressed with Control.

Super is never used to type text, so stop those key presses in the
entry's captured-event handler, before ClutterText sees them. Input
method events still go through. Shortcuts are unaffected, since
Main._stageEventHandler runs before the entry.
@mtwebster

Copy link
Copy Markdown
Member

I don't see a point to this, other than 'you can', and it potentially complicates grabs and keybindings in the future.

@mtwebster mtwebster closed this Nov 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants