In Visual Studio Code Ctrl+V is not working

Question

In Visual Studio Code Ctrl+V is not working on editor.

However from the command palette Ctrl+Shift+V is working.

Answer 1

I´ve had this problem when I enabled the "VIM" plugin for VSCode.

After uninstalling it, the problem was fixed.

Answer 2

Open the keyboard shortcuts preferences by pressing CTRL + SHIFT + P and search for open keyboard shortcuts file.

Then, search for the editor.action.clipboardPasteAction property. In your case, it might be CTRL+SHIFT+V. Try changing it to Ctrl + V. Like so:

Solution as of 2022

You could also CTRL + SHIFT + P and search for open keyboard shortcuts (JSON) and paste the following:

// Place your key bindings in this file to override the defaults
[
  {
    "key": "ctrl+v",
    "command": "-workbench.action.terminal.sendSequence",
    "when": "terminalFocus && !accessibilityModeEnabled && terminalShellType == 'pwsh'"
  },
  {
    "key": "ctrl+k",
    "command": "workbench.action.terminal.clear"
  }
]

Answer 3

@WebD'is answer is very helpful and I have upvoted it. But my comment focused on whether there was a conflicting binding for CTRL-V and how to find it. You can literally type "Ctrl+V" (note the "plus+" sign, not a hyphen) and it will find all keybindings that use that binding in whole or part. I suggest that there must be a something else also bound to CTRL-V.

---

Since this original answer, vscode introduced another way to see what other commands might be bound to given keystrokes. With the Gear/Keyboard Shortcuts file open click on the little keyboardy icon to the right (or Alt+K with this file open) and it will indicate Recording Keys next to it. Now you can literally press Ctrl+V (or whichever keybinding you are interested in) and those corresponding commands, if any, that use that keybinding will be filtered up.

Remember to disable the Recording Keys functionality by clicking the keyboardy icon if you want to go back to regular searching in the Keyboard Shortcuts file.

Answer 4

If you install the vim extension for visual studio code and find that ctrl + x, ctrl + v .. or other shortcuts stopped working, this is because they are overwritten by extension.vim_

If you prefer to get those shortcuts back go to keyboard shortcuts (ctrl + shift + p, then search for open keyboard shortcuts file).

• Search for extension.vim_ and check too see if any shortcuts are assigned to your key combination like ctrl + v. Remove it (right click, delete).
• Also check for any other conflict by searching the file.
• Save the file, it should work now.

Answer 5

I have the same problem: can't CTRL+X, CTRL+C, CTRL+V on VSCode editor. I uninstall the Vim extension and the problem is fixed.

Answer 6

For future searchers who do not have Vim (or any other extension) installed which is causing the issue, and who might have verified that their keyboard bindings are correct....

I have the Salesforce Extension Pack installed and had right-clicked on a file and run SFDX: Deploy Source to Org. The deployment had errors, so in the Panel area (which I have at the bottom of my screen) [see image] I had clicked on both the OUTPUT and PROBLEMS tabs, which shifted focus away from my PowerShell TERMINAL tab.

My Ctrl-V issue was when I was trying to correct my Apex code in the EDITOR pane. Ctrl-V was not pasting the code I had just Cut or Copied (but right-clicking and choosing Paste was working).

I ultimately discovered, when I changed my Panel focus back to my PowerShell TERMINAL tab, that ALL of the Ctrl-V pasting I had attempted had shown up after my PowerShell prompt! ["circled" in blue in image]

---

tl;dr

Make sure your pasted text did not show up in your TERMINAL - even if it is not in focus or even if your cursor is in another Panel tab or in the EDITOR.

Answer 7

From File > Performance > Keyboard Shortcuts > search paste > just try to remove or rest some keybinding with right click on paste or default:paste

Answer 8

This problem happened to me after I left VSC update itself (currently 1.53.0). It had been converted to Shift-Insert.

Go to File->Preferences->Keyboard shortcuts. Find the editor.action.clipboardPasteAction and double click it, then type Ctrl+V.

Answer 9

If you have the Vim extension installed, you may set the vim.useSystemClipboard in the vim extension setting to true. Then you can paste the content from the clipboard by simply pressing p in the NORMAL mode, or use Ctrl+V in the INSERT mode.

Answer 10

+1 for this - in case this helps anyone:

In my case it was only happening in the Thunder Client extension's text fields.

The culprit for me was the Indent on Paste extension (I'm on a Mac, so it was cmd+v instead of ctrl+v - but it fires the same event in VS Code).

I've left issue comments on the Thunder Client and Indent on Paste repos respectively, should anyone wish to add to those.

Answer 11

Look if and remove any VS Code extension : for example - "Awesome Emacs Keymap" in my case, or any other keymaps installed.

i.e. : FILE/Preferences>/extensions and then look if any special keymap was installed

Answer 12

Modify the setting of vscode: Settings - input:vim ctrl key - unselect: Enale some vim ctrl key commands that override otherwise common operations, like ctrl + c

Answer 13

go to extensions search Emacs keymap and uninstall it

Answer 14

There should something conflicting to your any previous keyboard shortcut like in my case for Change All Occurrence: (Ctrl-C + Ctrl-A), vs code, confused with Ctrl-C for a copy shortcut to this : (Ctrl-C + Ctrl-A), so I change this to (Shift-C + Shift-A), My Issue resolved.

Answer 15

Go to File>Preference>keyboard Shortcuts Then Check for Copy and paste and enter the Ctrl+C and Ctrl+v shortcuts

Happy Coding ;)

Answer 16

None of the issues above solved this for me. I had a key binding Ctrl+C Ctrl+L. So when I pressed Ctrl+C it was in a state where it was waiting for the next key to be pressed and wouldn't do anything.

This showed up in the toolbar like so (an example):

This didn't come up in the list of keybindings when searching for Ctrl+C. So I found it be looking through the list.

Answer 17

Remove all cmd+v or in windows ctrl+v associated keybindings.

Answer 18

For me the solution was going through my extensions and disabling them one by one to find the culprit.

I had 'Paste and Indent' enabled which was messing up copying and pasting.

Just had to disable it and reload vs code.

Answer 19

Open Settings > keyboard shortcuts

Search for Ctrl + c

Delete the mapping for vim.

Answer 20

i have same problem step:1

ctrl+shift+p

step:2 find

Open keyboard shortcuts

step:3

find paste

then you can see

editor.action.cliboardPasteAction 

1. right click then changekeybinding if key wrong

2. or remove key if u found two same line(editor.action.cliboardPasteAction)

in my case is 2nd one(so i removed)

Answer 21

In my case just the relaunch of VSCode solved the issue. My key bindings were fine.

Answer 22

In some cases, if you use remote ssh connects to a remote server and code there, ctrl + V may not be useful because that your remote server has a high balance, you can try to uninstall some useless plugins in that remote server then reload vscode.

Answer 23

"Paste JSON as Code" was my offender, as well as a few other ones. I got a little extension happy there for a bit.

Answer 24

I have disabled all extensions, and VS Code hangs for a few seconds whenever I try to paste something. This occurs with Ctrl+V, Shift+Ins and also with right click + Paste.

It hangs, and then nothing happens.

[UPDATE] I simply reinstalled it, and that solved the issue for me.

Answer 25

Its easy don't worry, you need to search using ctrl+shift+p and find Prefernces: Open Keyboard Shortcuts(JSON) and add this dict

// Place your key bindings in this file to override the defaults
[
    {
        "key": "ctrl+c",
        "command": "editor.action.clipboardCopyAction",
        "when": "textInputFocus"
    }
]

I thins it's very helpfull good luck :)

Answer 26

If you did everything above, but you still cannot use ctrl+c, ctrl+v to copy paste in terminal, this is the fix:

ctrl + shift + p, then search for settings.json, and click Open User Settings (JSON):

make sure you have this line in it:

{
...
"terminal.integrated.sendKeybindingsToShell": false,
...
}

Then, ctrl + shift + p, then search for keyboard shortcuts, and click Open Keyboard Shortcuts (JSON):

Delete everything, and paste this in it:

// Place your key bindings in this file to override the defaultsauto[]
[
    {
        "key": "ctrl+v",
        "command": "workbench.action.terminal.paste",
        "when": "terminalFocus && terminalHasBeenCreated || terminalFocus && terminalProcessSupported"
    },
    {
        "key": "ctrl+shift+v",
        "command": "-workbench.action.terminal.paste",
        "when": "terminalFocus && terminalHasBeenCreated || terminalFocus && terminalProcessSupported"
    },
    {
        "key": "ctrl+c",
        "command": "workbench.action.terminal.copySelection",
        "when": "terminalFocus && terminalHasBeenCreated && terminalTextSelected || terminalFocus && terminalProcessSupported && terminalTextSelected"
    },
    {
        "key": "ctrl+shift+c",
        "command": "-workbench.action.terminal.copySelection",
        "when": "terminalFocus && terminalHasBeenCreated && terminalTextSelected || terminalFocus && terminalProcessSupported && terminalTextSelected"
    }
]

Answer 27

In my case everything was solved changing into Ctrl + v here:

workbench.action.terminal.paste:

Answer 28

**For 2023 coders : **.
If your shortcut keys such as Ctrl+C & Ctrl+V not working ( neither in code file nor in Terminal ), no need to worry 😄

Try : Ctrl+insert (for copy) , Shift+insert (for paste )

Answer 29

In my case it was not taking the latest text copied in clipboard,

I have removed the key bindings of copy and paste associated (insert binding) was there except the ctrl + c & ctrl + v and restarted the vs code editor

keybindings (windows) -> ctrl + shift + p -> keyboard shortcuts

Answer 30

The issue for me was the extension "Eclipse Win Keymap". I uninstalled and made sure I have only the "Eclipse Keymap" and it is back to normal now.