starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Copying with Ctrl-Shift-C copies literal buffer, not lines #256

New Issue
Closed
opened 2026-01-30 21:46:57 +00:00 by claunia · 8 comments
claunia commented 2026-01-30 21:46:57 +00:00
Owner
Copy Link

Originally created by @parkovski on GitHub (May 10, 2018).

Selecting text and copying with Ctrl-Shift-C copies the buffer literally, which gives a line full of spaces and no newline. Copying with right click works as intended. Verified in cmd.exe, pwsh.exe and zsh.

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

  • What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots)

PS> echo "foo`nbar"
foo
bar
PS> # copy those two lines with Ctrl-Shift-C and paste into notepad
PS> # should have a line full of spaces before "bar"
  • What's wrong / what should be happening instead:
    It should do the same thing as right click copy - lines have a new line at the end instead of being filled with spaces.
Originally created by @parkovski on GitHub (May 10, 2018). Selecting text and copying with Ctrl-Shift-C copies the buffer literally, which gives a line full of spaces and no newline. Copying with right click works as intended. Verified in cmd.exe, pwsh.exe and zsh. * Your Windows build number: (Type `ver` at a Windows Command Prompt) 17666 * What you're doing and what's happening: (Copy & paste specific commands and their output, or include screen shots) ``` PS> echo "foo`nbar" foo bar PS> # copy those two lines with Ctrl-Shift-C and paste into notepad PS> # should have a line full of spaces before "bar" ``` * What's wrong / what should be happening instead: It should do the same thing as right click copy - lines have a new line at the end instead of being filled with spaces.
claunia added the Product-ConhostWork-ItemNeeds-TriageIssue-TaskArea-Interaction labels 2026-01-30 21:46:57 +00:00
claunia commented 2026-01-30 21:46:58 +00:00
Author
Owner
Copy Link

@MichaelTong commented on GitHub (Jul 18, 2018):

This still happens on 17713.

@MichaelTong commented on GitHub (Jul 18, 2018): This still happens on 17713.
claunia commented 2026-01-30 21:46:58 +00:00
Author
Owner
Copy Link

@tombrown52 commented on GitHub (Jan 19, 2019):

This still happens on 1809 (17763).

It seems to me that copy and paste should behave the same, whether done via the mouse (right-click) or keyboard (ctrl+shift+c/v).

As it is, all the extra spaces and lack of newlines makes the keyboard shortcut ctrl+shift+c useless for all but the most simple selections.

@tombrown52 commented on GitHub (Jan 19, 2019): This still happens on 1809 (17763). It seems to me that copy and paste should behave the same, whether done via the mouse (right-click) or keyboard (ctrl+shift+c/v). As it is, all the extra spaces and lack of newlines makes the keyboard shortcut ctrl+shift+c useless for all but the most simple selections.
claunia commented 2026-01-30 21:46:58 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (Jan 22, 2019):

I've filed MSFT: 20265934 to look into this.

@miniksa commented on GitHub (Jan 22, 2019): I've filed MSFT: 20265934 to look into this.
claunia commented 2026-01-30 21:46:58 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 22, 2019):

Actually this one might be by design. IIRC, Ctrl-Shift-C always had this behavior, and it always worked, even w/o the "copy/paste with Ctrl-Shift-C/V" checkbox.

Either we should change the text to just say "Paste with Ctrl-Shift-V", or override the usual copy behavior (copy literally) when that box is checked and replace it with the default copy behavior

@zadjii-msft commented on GitHub (Jan 22, 2019): Actually this one might be by design. IIRC, Ctrl-Shift-C always had this behavior, and it always worked, even w/o the "copy/paste with Ctrl-Shift-C/V" checkbox. Either we should change the text to just say "Paste with Ctrl-Shift-V", or override the usual copy behavior (copy literally) when that box is checked and replace it with the default copy behavior
claunia commented 2026-01-30 21:46:59 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (Jan 22, 2019):

The latter is what I'm thinking and why I filed 20265934, @zadjii-msft.

@miniksa commented on GitHub (Jan 22, 2019): The latter is what I'm thinking and why I filed 20265934, @zadjii-msft.
claunia commented 2026-01-30 21:46:59 +00:00
Author
Owner
Copy Link

@miniksa commented on GitHub (May 14, 2019):

Moving back to tracking the work here. Here's the comments from the internal issue for whenever I get back to it:

I think what's happening here is that the copy feature already had a VK_SHIFT alternate behavior and that's getting caught up in the new Ctrl+Shift+C feature to enable WSL copying.

@miniksa commented on GitHub (May 14, 2019): Moving back to tracking the work here. Here's the comments from the internal issue for whenever I get back to it: I think what's happening here is that the copy feature already had a VK_SHIFT alternate behavior and that's getting caught up in the new Ctrl+Shift+C feature to enable WSL copying.
claunia commented 2026-01-30 21:46:59 +00:00
Author
Owner
Copy Link

@fumin commented on GitHub (Jan 29, 2026):

What kind of f*ckery is this!?
It's the year 2026, and stupid Windows can't even copy plain text!?

@fumin commented on GitHub (Jan 29, 2026): What kind of f*ckery is this!? It's the year 2026, and stupid Windows can't even copy plain text!?
claunia commented 2026-01-30 21:46:59 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jan 29, 2026):

You know, it looks like this bug was filed against the Windows Console Host shortly after line wrapping support even shipped. That's closer to when it shipped broken than it is to today. I'm closing this out - unless somebody can demonstrate it reproducing in Windows Terminal with a shell that actually emits long, and wrappable, lines.

@DHowett commented on GitHub (Jan 29, 2026): You know, it looks like this bug was filed against the Windows Console Host shortly after line wrapping support _even shipped._ That's closer to when it shipped broken than it is to today. I'm closing this out - unless somebody can demonstrate it reproducing in Windows Terminal with a shell that actually emits long, and wrappable, lines.
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 Area-Interaction Issue-Task Needs-Triage Product-Conhost Work-Item
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#256
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?