Waiting for second key of chord

Question

I have assigned the keyboard shortcut Ctrl+E to a command. But when I click Ctrl+E, the status bar says Ctrl+E

Answer 1

I have had the same issue with my "<" [backquote] key and wasn't able to find the right keybinding in the normal settings. Allow chords wouldn't do anything either.

This is for anyone, who isn't able to reasign the key in the default keybindings:

1. Find the User settings in your terminal.

    Windows %APPDATA%\Code\User\

    macOS $HOME/Library/Application Support/Code/User/

    Linux $HOME/.config/Code/User/

2. Open the keybindings.json file
3. look for all chords that you would like gone.
4. (Obviously) remove/alter them

I hope I could help some of you!

Answer 2

I came to this question because I had the same problem as the OP, but in the Integrated Terminal. My problem:

I couldn't stop the node server by doing Ctrl+C, because my VS Code was waiting for the "second key of chord"...

I fixed it in the user settings, by unchecking the Allow Chords checkbox.

I answered the more suitable question for me here.

Answer 3

Key chords are a keyboard shortcut feature of Visual Studio. They consist of a sequence of key presses like (Ctrl+K, Ctrl+C) for comment code or (Ctrl+K, Ctrl+U) for uncomment code.

They are activated by the user pressing one Ctrl+key combination, then another Ctrl+key combo. For example Ctrl+K, Ctrl+C on my install of Visual Studio is used for commenting selected text.

In your case, Ctrl+E is a common chord starter and is used by many chords. For example Ctrl+E, Ctrl+W = Toggle Word Wrap and Ctrl+E, Ctrl+X = Workspace Designer.ExpandAll.

The reason you see the error is because Visual Studio has it mapped to other chords. Because of this, you cannot use Ctrl+E by itself for a keyboard shortcut

But, you can create your own chord, Ctrl+E, Ctrl+D is not in use on my install of Visual Studio 2012.

And your question is not the same as the other question. In that question, the OP has started the chord process (Ctrl+E) and wants to cancel Visual Studio from waiting for the 2nd chord key.

Edit: You can use Ctrl+E as a standalone shortcut under some conditions. It might depend on what developer settings you have enabled in Visual Studio. Also if you remove all key chords that start with (Ctrl+E) then it can work as a non-chord shortcut.

Answer 4

1. To see which commands are using your keyboard shortcut at the moment, enter it in the "Press shortcut keys:" edit box. Make sure you don't accidentally click "Assign".
2. In the dropdown box "Shortcut currently used by:" you can browse through and manually remove all commands that currently occupy your desired shortcut combination.

Answer 5

Do

ctrl+ E

then

ctrl + V

More info here:

Answer 6

The selected answer is wrong in stating you cannot use Ctrl+E by itself (at least for Visual Studio 2013).

For those who come from a Mac or other OS background where Ctrl+E takes you to the end of the current line (the End key shortcut by default in VS), this is a really frustrating limitation when switching environments.

I found that in Visual Studio 2013 at least, you can remove all the shortcuts that use the Ctrl+E chord (none of which I will ever use) and set the Edit.LineEnd command to Ctrl+E. It just takes a few minutes tracking down the chords to remove (most of them are under the workspace designer).