xterm still uses the middle mouse button to paste (and most certainly not Ctrl-V), because they're old-school that way. VSCode (actually xtermjs) went with Ctrl-V for their own reasons. Which is not dissimilar to how wsltty chose to do their paste operation, for the same reasons, although wsltty went with the more traditional paradigm of Ctrl/Shift+Ins. Which the console team chose to do in order to quoth 'ensure that we don't break any existing behaviors'. The paste operation in Windows Console with WSL is Ctrl+Shift+C/V per Rich's blog post.
This behavior suggests it's the command prompt window Windows ConsoleĬorrect. Strangely, Ctrl+V does paste inside the VS Code integrated terminal
But to be clear:įilter clipboard contents on paste: ticked My settings in Alt+Space->Properties are default, afaik. Strace of the failing command, if applicable: N/A I would expect Ctrl+V to just paste the copied text, just like in the regular command prompt (cmd.exe) where it works totally fine. Only the right mouse button successfully pastes text. What's wrong / what should be happening instead: Pressing Ctrl+V inserts ^V into the terminal, rather than copied text. What you're doing and what's happening: Trying to paste text into the console, but all I'm getting is ^V, which is probably some archaic escape character that noone needs anymore.
