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

Formatting issues when pasting in WSL tab #4896

New Issue
Closed
opened 2026-01-30 23:59:39 +00:00 by claunia · 3 comments
claunia commented 2026-01-30 23:59:39 +00:00
Owner
Copy Link

Originally created by @ghost on GitHub (Nov 9, 2019).

Environment

Windows build number: Microsoft Windows [Version 10.0.19018.1]
Windows Terminal version (if applicable): 0.6.2951.0
WSL version: 2
WSL distribution: Ubuntu

Steps to reproduce

Copy any text with multiple lines into the WSL terminal tab.
Note: this bug does NOT occur in the command line and PowerShell tabs.

Expected behavior

Same amount of lines as in the source and the paste not affecting existing text in unexpected ways.

Actual behavior

I get extra lines in-between regardless of whether the source I copy from is LF or CRLF when I paste it into WSL in the terminal.
image
image

Existing text is also affected.

before:
image
after:
image

another example:

before:
image
after:
image

Originally created by @ghost on GitHub (Nov 9, 2019). # Environment ```none Windows build number: Microsoft Windows [Version 10.0.19018.1] Windows Terminal version (if applicable): 0.6.2951.0 WSL version: 2 WSL distribution: Ubuntu ``` # Steps to reproduce <!-- A description of how to trigger this bug. --> Copy any text with multiple lines into the WSL terminal tab. Note: this bug does NOT occur in the command line and PowerShell tabs. # Expected behavior Same amount of lines as in the source and the paste not affecting existing text in unexpected ways. <!-- A description of what you're expecting, possibly containing screenshots or reference material. --> # Actual behavior I get extra lines in-between regardless of whether the source I copy from is LF or CRLF when I paste it into WSL in the terminal. ![image](https://user-images.githubusercontent.com/47948375/68528431-512a6080-02fb-11ea-994a-970cf99170ff.png) ![image](https://user-images.githubusercontent.com/47948375/68528437-5edfe600-02fb-11ea-87b4-156d58460d64.png) Existing text is also affected. before: ![image](https://user-images.githubusercontent.com/47948375/68528480-e2013c00-02fb-11ea-9ab1-1c5239438602.png) after: ![image](https://user-images.githubusercontent.com/47948375/68528484-f5aca280-02fb-11ea-9e56-c385bf8a345d.png) another example: before: ![image](https://user-images.githubusercontent.com/47948375/68528500-1e349c80-02fc-11ea-9be3-855ae2e2c397.png) after: ![image](https://user-images.githubusercontent.com/47948375/68528508-36a4b700-02fc-11ea-9b79-728b8fe24413.png)
claunia added the Resolution-Duplicate label 2026-01-30 23:59:39 +00:00
claunia commented 2026-01-30 23:59:40 +00:00
Author
Owner
Copy Link

@d-bingham commented on GitHub (Nov 9, 2019):

This is, as far as I can tell, a duplicate of #1091 and was fixed in #3449.

I just checked this with the current build (specifically with nano, as I don't actually use it as part of my workflow, and its handling of some terminal settings is different than, say, vi. Also I've been doing development for a long time and that causes paranoia), and it looks like it's working.

So it's working in the live build off the repository, and it'll be in 0.7.

@d-bingham commented on GitHub (Nov 9, 2019): This is, as far as I can tell, a duplicate of #1091 and was fixed in #3449. I just checked this with the current build (specifically with nano, as I don't actually use it as part of my workflow, and its handling of some terminal settings is different than, say, vi. Also I've been doing development for a _long_ time and that causes paranoia), and it looks like it's working. So it's working in the live build off the repository, and it'll be in 0.7.
claunia commented 2026-01-30 23:59:40 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 9, 2019):

Glad to hear it. When is 0.7 being released?

@ghost commented on GitHub (Nov 9, 2019): Glad to hear it. When is 0.7 being released?
claunia commented 2026-01-30 23:59:40 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Nov 9, 2019):

@europasich somewhat approximately following the roadmap 😄

@d-bingham thanks for hooking up the duplicate!

@DHowett-MSFT commented on GitHub (Nov 9, 2019): @europasich somewhat approximately following [the roadmap](https://github.com/microsoft/terminal/blob/master/doc/terminal-v1-roadmap.md#terminal-roadmap--timeline) :smile: @d-bingham thanks for hooking up the duplicate!
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 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#4896
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?