Press a shortcut chord in sequence, not all at once

01Read the binding in the shortcut editor

VS Code supports bindings made of more than one key combination. That differs from one combination containing several modifier keys.

When a reference shows two groups, inspect the command in the editor’s shortcut interface. Do not rely on spacing in an image: a generated graphic may make a sequence look like a crowded simultaneous press. Knowing the action name gives you a way to verify the intended notation instead of guessing a binding.

02Practise one known sequence

1. Choose a documented, harmless editor action and disposable content. Read the first combination, then the following one as a sequence, and observe the editor’s feedback.
2. Keep focus in the expected surface. If you lose the sequence, release and start again deliberately instead of adding unrelated keys. The aim is to understand the gesture, not force a particular timing result. Other apps may use different separators or use the word “chord” differently, so check their own instructions.

03Keep the app trigger separate

The gesture that opens KeyboardShortcuts.pro and a sequence displayed inside its reference are different settings. Clicking a reference row never executes the shown sequence.

Do not infer the utility’s opening trigger from a command’s displayed keys. If an editor sequence remains unreliable, inspect that editor’s conflicts, context and customizations. Avoid remapping a common system combination simply to imitate a diagram. Finish by identifying the ordered action the target app expects and how to check its current configuration.