Prefer later bindings in keymap section for display in UI (#23378)
Closes #23015 Release Notes: - Improved which keybindings are selected for display. Now later entries within `bindings` will take precedence. The default keymaps have been updated accordingly.
This commit is contained in:
parent
919703e6a8
commit
aacd80ee4a
11 changed files with 186 additions and 196 deletions
|
@ -32,8 +32,9 @@ impl PreprocessorContext {
|
|||
_ => return None,
|
||||
};
|
||||
|
||||
keymap.sections().find_map(|section| {
|
||||
section.bindings().find_map(|(keystroke, a)| {
|
||||
// Find the binding in reverse order, as the last binding takes precedence.
|
||||
keymap.sections().rev().find_map(|section| {
|
||||
section.bindings().rev().find_map(|(keystroke, a)| {
|
||||
if a.to_string() == action {
|
||||
Some(keystroke.to_string())
|
||||
} else {
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue