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

ssh newline problem #11417

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

Originally created by @CatCatCatDog on GitHub (Nov 15, 2020).

Windows terminal 1.4.3141.0
Windows 10 64bit 2004 (OS Build 19041.630)

What am i wrong? newline not work, If I open file and out from file.
only bug occur, on rmote Linux. not WSL

newline_problem

Originally created by @CatCatCatDog on GitHub (Nov 15, 2020). Windows terminal 1.4.3141.0 Windows 10 64bit 2004 (OS Build 19041.630) What am i wrong? newline not work, If I open file and out from file. only bug occur, on rmote Linux. not WSL ![newline_problem](https://user-images.githubusercontent.com/23658192/99179455-481b6d00-2761-11eb-9aca-b803d46f9119.png)
claunia added the Resolution-ExternalNeeds-Tag-Fix labels 2026-01-31 02:47:05 +00:00
claunia commented 2026-01-31 02:47:06 +00:00
Author
Owner
Copy Link

@jdebp commented on GitHub (Nov 15, 2020):

You should show the result of running the stty -a command on the remote system at this point. That's simple enough that you should be able to type it in without it being echoed back to you.

If it shows that the line discipline has local echo turned off with -echo, as it almost certainly will, then this is not a problem with Windows Terminal in any way and Windows Terminal is working as designed. This local echo mechanism is implemented in the line discipline in the kernel of the operating system on the remote host, not in Windows Terminal on your local machine.

People have been getting their terminals into this state by turning local echo off in their line disciplines, on Unix operating systems, since before Windows NT even existed. This and the "staircase effect" are two of the situations that are well-known and highly recognizable to long-time Unix and Linux-based operating system terminal users. You need to look to what you are doing on the remote host to its terminal line discipline, which isn't within the purview of a Windows Terminal bug report.

@jdebp commented on GitHub (Nov 15, 2020): You should show the result of running the `stty -a` command on the remote system at this point. That's simple enough that you should be able to type it in without it being echoed back to you. If it shows that the line discipline has local echo turned off with `-echo`, as it almost certainly will, then this is _not a problem with Windows Terminal_ in any way and Windows Terminal is working as designed. This local echo mechanism is implemented in the line discipline in the kernel of the operating system on the remote host, _not_ in Windows Terminal on your local machine. People have been getting their terminals into this state by turning local echo off in their line disciplines, on Unix operating systems, since before Windows NT even existed. This and the "staircase effect" are two of the situations that are well-known and highly recognizable to long-time Unix and Linux-based operating system terminal users. You need to look to what you are doing _on the remote host_ to its terminal line discipline, which isn't within the purview of a Windows Terminal bug report.
claunia commented 2026-01-31 02:47:06 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 16, 2020):

Thanks for the report! This is an upstream issue in Win32-OpenSSH (/dup https://github.com/PowerShell/Win32-OpenSSH/issues/1253), fixed in https://github.com/PowerShell/openssh-portable/pull/426

@DHowett commented on GitHub (Nov 16, 2020): Thanks for the report! This is an upstream issue in Win32-OpenSSH (/dup https://github.com/PowerShell/Win32-OpenSSH/issues/1253), fixed in https://github.com/PowerShell/openssh-portable/pull/426
claunia commented 2026-01-31 02:47:06 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Nov 16, 2020):

Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!

@ghost commented on GitHub (Nov 16, 2020): Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!
claunia commented 2026-01-31 02:47:06 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Nov 16, 2020):

In short, exiting an alternate buffer or doing anything that might change the screen size (up to and including "launching a new SSH session") may cause output to be duplicated.

@DHowett commented on GitHub (Nov 16, 2020): In short, exiting an alternate buffer or doing anything that might change the screen size (up to and including "launching a new SSH session") may cause output to be duplicated.
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 Needs-Tag-Fix Resolution-External
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#11417
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?