Searching keyboard shortcuts with 'Record Keys' does not include chords using that keybinding #158799
Labels
*duplicate
Issue identified as a duplicate of another issue(s)
keybindings-editor
Keybinding editor issues
Type: Feature Request
If you use 'Record Keys' in the keyboard shortcuts settings to search for a keybinding (say, because you want to see if it's available, or why it's not triggering as you'd expect), you only see exact matches for that binding, not any chords that might use it as a prefix. This can be misleading if you aren't aware of this behavior.
As a default, it might be better for 'Record Keys' to use the un-quoted search string, so chords would show up as well.
I installed an extension which added keybindings using
cmd+l
as the first key in a chord. When the default behavior of plaincmd+l
stopped working, I searched keyboard shortcuts (using Record Keys) for"cmd+l"
to see if something had overridden it. Since the extension's keybinding didn't show up in that search (since it wascmd+l cmd+o
), I believed something more complex was going on, and went through a whole extension bisect to realize that it was indeed just a simple keybinding issue.Example:
"cmd+k"
is the first shortcut in many, many chords."cmd+k"
show up, not all the bindings that start with that prefix.cmd+k
), then all matches show up, including chords.VS Code version: Code 1.70.2 (e4503b3, 2022-08-16T05:36:37.829Z)
OS version: Darwin x64 20.6.0
Modes:
The text was updated successfully, but these errors were encountered: