You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
Activity
jdebp commentedon Nov 15, 2020
You should show the result of running the
stty -acommand 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.
DHowett commentedon Nov 16, 2020
Thanks for the report! This is an upstream issue in Win32-OpenSSH (/dup PowerShell/Win32-OpenSSH#1253), fixed in PowerShell/openssh-portable#426
DHowett commentedon 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.