tmux exception in windows terminal

[zhang-stephen]

Windows Terminal version (or Windows build number)

windows 10.0.183631743, terminal 1.10.1933.0 preview

Other Software

openSUSE tumbleweed 202108xx in virtual box
SSH for windows 8.1p1
tmux 3.2a
Z-Shell 5.8

Steps to reproduce

start the openSUSE VM, connect to it in windows terminal via ssh, and run tmux in windows terminal, you will see the ^[[>0;10;1c; as mentioned in tmux: #2844.

I have tried PuTTY and MobaXterm 20, this issue seems only be reproduced in windows terminal. and the maintainer of tmux thought it's a bug/incorrect behavior from terminal, could you help to investigate this problem?

Expected Behavior

the ^[[>0;10;1c; should not be printed on screen.

Actual Behavior

the ^[[>0;10;1c; printed on screen.

[elsaco]

From tmux manual:

 escape-time time
         Set the time in milliseconds for which tmux waits after an escape is input to determine if it is part of
         a function or meta key sequences.  The default is 500 milliseconds.

@Stark-Zhang is the issue still present if you add "set -sg escape-time 10" to your .tmux.conf to increase the time from default?

@Stark-Zhang is this happening when connecting to a remote system also?

[zadjii-msft]

Does this repro if you use a vintage console window (i.e conhost.exe) to run ssh.exe?

If you use ssh from a WSL distro instead of ssh.exe, does the issue still happen? (Just trying to remove variables here - Terminal running ssh.exe connected to a machine running tmux is a lot of moving parts. )

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

[zhang-stephen]

Does this repro if you use a vintage console window (i.e conhost.exe) to run ssh.exe?

If you use ssh from a WSL distro instead of ssh.exe, does the issue still happen? (Just trying to remove variables here - Terminal running ssh.exe connected to a machine running tmux is a lot of moving parts. )

1. I tried run ssh.exe in PowerShell 7 and this issue reproduced.
2. It's not reproduced in WSL Ubuntu 20.04.3

[zhang-stephen]

From tmux manual:

 escape-time time
         Set the time in milliseconds for which tmux waits after an escape is input to determine if it is part of
         a function or meta key sequences.  The default is 500 milliseconds.

@Stark-Zhang is the issue still present if you add "set -sg escape-time 10" to your .tmux.conf to increase the time from default?

@Stark-Zhang is this happening when connecting to a remote system also?

1. this would reproduce if configured as you said.
2. this didn't reproduce on other remote system, such as CentOS or RHEL, even keep the default configuration.

[iBug]

I can reproduce this on a remote Ubuntu host over OpenSSH. On tmux startup there's the strange 0;10;1c printed on tmux. This doesn't happen with conhost.exe (running ssh.exe <remote> from CMD window). Ubuntu 20.04 (tmux 3.0a) and 22.04 (tmux 3.2a) are both affected.