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

Feature request: Add redundant \r on line wrap #7242

New Issue
Closed
opened 2026-01-31 00:58:47 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 00:58:47 +00:00
Owner
Copy Link

Originally created by @rovf on GitHub (Apr 1, 2020).

This feature request evolves from a discussion about mintty (Cygwin) not working correctly with the new winpty anymore.The problem is that copying a line longer than the terminal width, which is being output by a typical Windows console (i.e. non-Cygwin) program from the mintty terminal, causes a hard line break being inserted in the copied string, because the controlling terminal (mintty in this case), can not recognize whether the line is really a long line having been wrapped around, or two short lines, where the first of these happened to be exactly the Window width.

I want to select with the mouse a long line which has been wrapped around, and paste it somewhere, without getting a hard line break at the point where the line wrap has occured.

Proposed technical implementation details (optional)

Since there seems to be no really good alternative, the mintty maintainer suggested that winpty would output \r\r\n, if there is a wrap around of the line. The redundant \r would signal to the controlling terminal, that a line wrap has occured.

Originally created by @rovf on GitHub (Apr 1, 2020). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> This feature request evolves from a [discussion about mintty (Cygwin) not working correctly](https://github.com/mintty/mintty/issues/971) with the new winpty anymore.The problem is that copying a line longer than the terminal width, which is being output by a typical Windows console (i.e. non-Cygwin) program from the mintty terminal, causes a hard line break being inserted in the copied string, because the controlling terminal (mintty in this case), can not recognize whether the line is really a long line having been wrapped around, or two short lines, where the first of these happened to be exactly the Window width. <!-- A clear and concise description of what you want to happen. --> I want to select with the mouse a long line which has been wrapped around, and paste it somewhere, without getting a hard line break at the point where the line wrap has occured. # Proposed technical implementation details (optional) Since there seems to be no really good alternative, the mintty maintainer suggested that winpty would output \r\r\n, if there is a wrap around of the line. The redundant \r would signal to the controlling terminal, that a line wrap has occured.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 00:58:47 +00:00
claunia commented 2026-01-31 00:58:48 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 1, 2020):

So this is actually a bug that we're already tracking in #5113, and I'm trying to fix over in #5181. The real solution to this problem shouldn't be "add another hack to make this scenario work", the solution is just "don't hard break lines"

/dup #5113

p.s. winpty != conpty. winpty is a third party library for creating pseudoterminals on Windows, and ConPTY is the set of APIs that we maintain for hosting "pseudo-consoles". They're similar, but we only maintain conpty 😉

@zadjii-msft commented on GitHub (Apr 1, 2020): So this is actually a bug that we're already tracking in #5113, and I'm trying to fix over in #5181. The real solution to this problem shouldn't be "add another hack to make this scenario work", the solution is just "don't hard break lines" /dup #5113 p.s. winpty != conpty. winpty is a third party library for creating pseudoterminals on Windows, and ConPTY is the set of APIs that we maintain for hosting "pseudo-consoles". They're similar, but we only maintain conpty 😉
claunia commented 2026-01-31 00:58:48 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 1, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Apr 1, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
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 Issue-Feature Resolution-Duplicate
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#7242
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?