| Summary: | Rebindable keys for global menu | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | hiphish |
| Component: | Global Menu widget | Assignee: | Kai Uwe Broulik <kde> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | wishlist | CC: | kde, mvourlakos, nate, plasma-bugs-null |
| Priority: | VLO | ||
| Version First Reported In: | 5.21.5 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
hiphish
2021-05-17 21:43:16 UTC
This kind of opens up a bit of a can of worms. Why just the global menu? That would be weird and inconsistent. We would want it in KRunner and Kickoff too. And QStyle-based menus as well. And list views. So in short, this ideally should be a "global vi mode navigation support" thing, and not a "support vi mode navigation in the global menu applet" thing. But if you do that, you'll start bumping into existing behaviors where the letter keys do different things. I question whether it is possible to do this in a clean way... > Why just the global menu? Unline KRunner and Kickoff the global menu does not take text input. Plasmoids which take text input would need to be made modal, and there is no need for a vi-mode in those anyway since I can just type out what I want. > So in short, this ideally should be a "global vi mode navigation support" thing That would indeed be a massive can of worms. I don't think that making an entire desktop environment vi-like would be a good idea either. >I want to use vi-style keys instead of arrow keys for easier accessibility.
System settings -> shortcuts -> navigation -> previous item in list.
This should be followed everywhere, but I can well believe it's not.
Please reopen if it is not.
(In reply to David Edmundson from comment #3) > System settings -> shortcuts -> navigation -> previous item in list. This does nothing for the global menu and it requires a modifier key like Ctrl, a letter key alone cannot be used. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |