starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Copy and paste no longer works in WSL - as of 11/9 #92

New Issue
Closed
opened 2026-01-30 21:42:09 +00:00 by claunia · 11 comments
claunia commented 2026-01-30 21:42:09 +00:00
Owner
Copy Link

Originally created by @bitcrazed on GitHub (Feb 16, 2018).

From @neovaldivia on November 14, 2017 18:57

  • Your Windows build number: (Type ver at a Windows Command Prompt)
    version 10.0.15063

  • What you're doing and what's happening: (Copy&paste specific commands and their output, or include screen shots)
    Copy and paste is not working in any console drive app: WSL, cmd, GitBash

  • What's wrong / what should be happening instead:
    I have tried hotkeys (enabled in Properties/Quick Edit mode), With no result at all
    I have tried using the menu at the title bar, with no result.
    Copy and paste work for all other GUI apps but not in console, it does produce any result.

  • Strace of the failing command, if applicable: (If <cmd> is failing, then run strace -o strace.txt -ff <cmd>, and post the strace.txt output here)
    There is no command to run so I can't provide a strace

Copied from original issue: Microsoft/WSL#2667

Originally created by @bitcrazed on GitHub (Feb 16, 2018). _From @neovaldivia on November 14, 2017 18:57_ * Your Windows build number: (Type `ver` at a Windows Command Prompt) version 10.0.15063 * What you're doing and what's happening: (Copy&paste specific commands and their output, or include screen shots) Copy and paste is not working in any console drive app: WSL, cmd, GitBash * What's wrong / what should be happening instead: I have tried hotkeys (enabled in Properties/Quick Edit mode), With no result at all I have tried using the menu at the title bar, with no result. Copy and paste work for all other GUI apps but not in console, it does produce any result. * Strace of the failing command, if applicable: (If `<cmd>` is failing, then run `strace -o strace.txt -ff <cmd>`, and post the strace.txt output here) There is no command to run so I can't provide a strace _Copied from original issue: Microsoft/WSL#2667_
claunia added the Product-Conhost label 2026-01-30 21:42:09 +00:00
claunia commented 2026-01-30 21:42:11 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Feb 16, 2018):

From @jstarks on November 15, 2017 16:3

@bitcrazed This sounds like a console issue, not a WSL issue specifically. Can you help?

@bitcrazed commented on GitHub (Feb 16, 2018): _From @jstarks on November 15, 2017 16:3_ @bitcrazed This sounds like a console issue, not a WSL issue specifically. Can you help?
claunia commented 2026-01-30 21:42:11 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Feb 16, 2018):

From @zadjii-msft on November 16, 2017 17:36

Does copying text from somewhere, then pasting with right-click work in cmd, powershell, or bash? How about Shift-Insert?

Can you paste a screenshot of both the cmd and wsl properties sheet, on the "Options" tab? It should look like this:
image

Ctrl-V to paste never worked in WSL/bash, but I want to figure out what scenarios exactly do/don't work.

@bitcrazed commented on GitHub (Feb 16, 2018): _From @zadjii-msft on November 16, 2017 17:36_ Does copying text from somewhere, then pasting with right-click work in cmd, powershell, or bash? How about Shift-Insert? Can you paste a screenshot of both the cmd and wsl properties sheet, on the "Options" tab? It should look like this: ![image](https://user-images.githubusercontent.com/18356694/32906372-8f79abf4-cab1-11e7-9d45-c987f56eb8c9.png) Ctrl-V to paste *never* worked in WSL/bash, but I want to figure out what scenarios exactly do/don't work.
claunia commented 2026-01-30 21:42:11 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Feb 16, 2018):

From @neovaldivia on November 19, 2017 22:43

hey,
I found the issue is due to a incompatibility with Chrome for all console driven tools in the above Win version.
Current Chrome version: Version 62.0.3202.94 (Official Build) (64-bit)

Restarting chrome (killing all processes) allows to do all the Copy+Paste commands by design in each tool.

cheers

@bitcrazed commented on GitHub (Feb 16, 2018): _From @neovaldivia on November 19, 2017 22:43_ hey, I found the issue is due to a incompatibility with Chrome for all console driven tools in the above Win version. Current Chrome version: Version 62.0.3202.94 (Official Build) (64-bit) Restarting chrome (killing all processes) allows to do all the Copy+Paste commands by design in each tool. cheers
claunia commented 2026-01-30 21:42:11 +00:00
Author
Owner
Copy Link

@bitcrazed commented on GitHub (Feb 16, 2018):

@neovaldivia Also, Windows Console does not support pasting into a Linux distro using CTRL + V - this is something we're working on fixing, but we're confused as to how this is suddenly working for you, if you ARE running Windows Console.

Are you running a 3rd party terminal/console app?

@bitcrazed commented on GitHub (Feb 16, 2018): @neovaldivia Also, Windows Console does not support pasting into a Linux distro using CTRL + V - this is something we're working on fixing, but we're confused as to how this is suddenly working for you, if you ARE running Windows Console. Are you running a 3rd party terminal/console app?
claunia commented 2026-01-30 21:42:11 +00:00
Author
Owner
Copy Link

@joaopluigi commented on GitHub (Feb 20, 2019):

I'm not sure if I'm in the right issue, but for me CTRL+V never worked on WSL Bash.

On the integrated VSCode terminal (which calls the same .exe) works perfectly (even on vim). Instead of copying with CTRL+V, WSL adds a ^V character. I can make the paste work using the mouse right click, but it still does not work on vim.

Maybe @bitcrazed already answered that with:

Windows Console does not support pasting into a Linux distro using CTRL + V

I just wanted to be sure that we are on the same page.

@joaopluigi commented on GitHub (Feb 20, 2019): I'm not sure if I'm in the right issue, but for me CTRL+V never worked on WSL Bash. On the integrated VSCode terminal (which calls the same `.exe`) works perfectly (even on vim). Instead of copying with CTRL+V, WSL adds a `^V` character. I can make the paste work using the mouse right click, but it still does not work on vim. Maybe @bitcrazed already answered that with: > Windows Console does not support pasting into a Linux distro using CTRL + V I just wanted to be sure that we are on the same page.
claunia commented 2026-01-30 21:42:12 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 20, 2019):

@joaopluigi That's correct, Ctrl+V does not work as a shortcut to paste into WSL. You can however enable paste via Ctrl+Shift+V with the following property:

image

I don't believe this issue represents anything that's actionable anymore, so I'm gonna go ahead and close it.

@zadjii-msft commented on GitHub (Feb 20, 2019): @joaopluigi That's correct, Ctrl+V does not work as a shortcut to paste into WSL. You can however enable paste via Ctrl+Shift+V with the following property: ![image](https://user-images.githubusercontent.com/18356694/53128540-eb523a80-3519-11e9-9929-9e48176846da.png) I don't believe this issue represents anything that's actionable anymore, so I'm gonna go ahead and close it.
claunia commented 2026-01-30 21:42:12 +00:00
Author
Owner
Copy Link

@joaopluigi commented on GitHub (Feb 20, 2019):

@zadjii-msft Apparently, I don't see this property to enable in my console. I'm running Microsoft Windows [Version 10.0.17134.590] . Also, paste with CTRL+V on Command Prompt works fine, the problem for me is on WSL Bash.

@joaopluigi commented on GitHub (Feb 20, 2019): @zadjii-msft Apparently, I don't see this property to enable in my console. I'm running `Microsoft Windows [Version 10.0.17134.590]` . Also, paste with CTRL+V on `Command Prompt` works fine, the problem for me is on `WSL Bash`.
claunia commented 2026-01-30 21:42:12 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 20, 2019):

That setting was only added in 1809, which I believe is 10.0.17763.0.

The Console settings are the same properties across all commandline applications, though each app may have different settings. Case in point:
image

@zadjii-msft commented on GitHub (Feb 20, 2019): That setting was only added in 1809, which I believe is 10.0.17763.0. The Console settings are the same properties across all commandline applications, though each app may have different settings. Case in point: ![image](https://user-images.githubusercontent.com/18356694/53129204-d676a680-351b-11e9-8962-5a6b66ded4ed.png)
claunia commented 2026-01-30 21:42:12 +00:00
Author
Owner
Copy Link

@joaopluigi commented on GitHub (Feb 20, 2019):

@zadjii-msft Ok, thanks!

@joaopluigi commented on GitHub (Feb 20, 2019): @zadjii-msft Ok, thanks!
claunia commented 2026-01-30 21:42:12 +00:00
Author
Owner
Copy Link

@jaykrell commented on GitHub (Oct 31, 2021):

This is really bad.
I am seeing it on Windows 11.

@jaykrell commented on GitHub (Oct 31, 2021): This is really bad. I am seeing it on Windows 11.
claunia commented 2026-01-30 21:42:12 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 31, 2021):

@jaykrell this issue is nearly 4 years old - can you open a new issue? Make sure to include build numbers, Terminal versions, your settings.json, which shell you're using, etc.

@zadjii-msft commented on GitHub (Oct 31, 2021): @jaykrell this issue is nearly 4 years old - can you open a new issue? Make sure to include build numbers, Terminal versions, your `settings.json`, which shell you're using, etc.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Product-Conhost
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#92
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?