Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related to #2127 (doesn't fix since we still need a GTK UI)
This implements a UI for #2121. The most important part of this PR is the core cross-platform plumbing to get access to sequenced keybind information, not the UI itself. I think the UI itself could definitely use some love and improvement, and I'm happy for anyone to take that on. I think importantly, this gets us from no UI at all to some UI for key sequences.
This is macOS only. GTK shouldn't be hard to follow but would love any ideas (or even contributions) from our resident GTK experts, such as @jcollie @tristan957 etc.
Demo
The "pending key sequence" only shows up while a pending key sequence is active. Once a key sequence is complete (either through successfully executed an action or typing a key that isn't part of the sequence) then it disappears.