Dispatch a chord keybinding again if it is not followed by a second part

Does this issue occur when all extensions are disabled?: Yes/No

• VS Code Version: 1.63.2
• OS Version: MacOS Big Sur 11.6

Steps to Reproduce:

1. Type the default Cmd+K shortcut to clear the terminal => VS Code successfully catches the key down event but says Cmd+K is not a shortcut
2. In the keyboard shortcut settings, change the “Source” to “User” by changing the when condition to the same value than it already was set to.
3. Type Cmd+K => terminal successfully cleared
4. Click on “Reset key binding” => Doesn’t change anything except the “Source” column (because the when condition never changed), but it breaks the keyboard binding.

Demo: https://youtu.be/u6WXsDoErmw

[alexdima]

1. Even if this extension defined a CtrlK-CtrlR binding, and even if there is no “when condition”, that should not disable the Ctrl+K terminalFocused binding, right?

The keybinding rules defined by the extension do not have a when context. That means that they will be active in all contexts, even when the terminal has focus. This as designed. Please see keybindings documentation.

1. Considering this extension seems to mess bindings up, it seems shady that it does break the Ctrl+K “clear terminal” binding when it’s in “Default” mode but doesn’t break it when it’s in “User” mode as shown in the video in my initial post.

Can you please provide clear steps that reproduce a problem but which don’t involve installing the problematic extension?

[8BitRobot]

Here’s an alternative idea: what if VS Code provides the option to create keybindings of multiple keys and one modifier? As in, the user can hold down cmd while they press k and g; if they let go of cmd it registers the cmd+k, and if they add a g while still holding down cmd it’ll register the whole shortcut cmd+k cmd+g?

I’ve stumbled into this issue myself by trying to create a keymap that resembles the IPA keyboard shortcuts here. In this website, it binds alt+a to one character, alt+a+a to another, and so on. The number of times you press the second character while still holding down alt is what determines the character being typed.