After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 665318 - add a keybinding to open the app menu
add a keybinding to open the app menu
Status: RESOLVED DUPLICATE of bug 672909
Product: gnome-shell
Classification: Core
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2011-12-01 18:46 UTC by Matthias Clasen
Modified: 2012-05-07 14:04 UTC
See Also:
GNOME target: 3.6
GNOME version: ---



Description Matthias Clasen 2011-12-01 18:46:12 UTC
This will make life easier when we start adopting the app menu seriously.
Comment 1 Allison Karlitskaya (desrt) 2011-12-09 14:49:10 UTC
This strongly implies the want of mnemonics in the menu...
Comment 2 Matthias Clasen 2011-12-09 17:38:55 UTC
I don't think so.
You want a fixed, unchanging key combination for this.
Something like Alt-F3.
Comment 3 Allison Karlitskaya (desrt) 2011-12-09 18:33:53 UTC
But after you hit Alt-F3 you might expect to be able to hit 'X' to activate the item inside the menu...
Comment 4 Matthias Clasen 2011-12-09 18:56:22 UTC
none of the other shell menus have mnemonics
Comment 5 Allison Karlitskaya (desrt) 2011-12-09 22:41:33 UTC
and (afaik) they don't have hotkeys to access them

of course, you could do alt+f3, down, down, down, down, enter... but that leaves something to be desired...
Comment 6 Matthias Clasen 2012-05-07 12:57:18 UTC
I think this should probably be a blocker, considering we're now pushing for widespread adoption of app menu in 3.6
Comment 7 Florian Müllner 2012-05-07 13:27:23 UTC
(In reply to comment #6)
> I think this should probably be a blocker, considering we're now pushing for
> widespread adoption of app menu in 3.6

Except that we've had that keybinding since 3.4.1 :-)

*** This bug has been marked as a duplicate of bug 672909 ***