Escape sequence inserted around prompt when starting tmux in an ssh session #17075

Closed
opened 2026-01-31 05:31:32 +00:00 by claunia · 3 comments
Owner

Originally created by @gurka on GitHub (Mar 24, 2022).

Windows Terminal version

1.11.3471.0

Windows build number

10.0.19044.0

Other Software

OpenSSH_8.1p1 for Windows,
Hyper-V VM running Debian testing/bookworm
GNU bash, version 5.1.16
tmux 3.2a

Steps to reproduce

Start Windows Terminal
Connect to Linux VM using ssh.exe
In bash, start tmux

Expected Behavior

First line / prompt displays:

simon@debian:~$

Actual Behavior

First line / prompt displays:

^[[>0;10;1csimon@debian:~$ 0;10;1c
Originally created by @gurka on GitHub (Mar 24, 2022). ### Windows Terminal version 1.11.3471.0 ### Windows build number 10.0.19044.0 ### Other Software OpenSSH_8.1p1 for Windows, Hyper-V VM running Debian testing/bookworm GNU bash, version 5.1.16 tmux 3.2a ### Steps to reproduce Start Windows Terminal Connect to Linux VM using ssh.exe In bash, start tmux ### Expected Behavior First line / prompt displays: ``` simon@debian:~$ ``` ### Actual Behavior First line / prompt displays: ``` ^[[>0;10;1csimon@debian:~$ 0;10;1c ```
claunia added the Issue-BugResolution-Duplicate labels 2026-01-31 05:31:32 +00:00
Author
Owner

@gurka commented on GitHub (Mar 24, 2022):

Note: this works OK with Powershell instead of Windows Terminal. Haven't verified any other terminal emulators, but I'm pretty sure that it works OK in PuTTY as well.

There are few bug tickets in other projects, like https://github.com/microsoft/WSL/issues/5931, but in my scenario it seems Windows Terminal is the culprit - hence the ticket here. Also for me this happens every time while in those other tickets it seems to happen randomly.

TERM is xterm-256colors before starting tmux and tmux-256colors after starting tmux, both when using Windows Terminal and Powershell.

And like in those other tickets I'm also using set -s escape-time 0 in my .tmux.conf. Setting this to 50 solves the issue.

@gurka commented on GitHub (Mar 24, 2022): Note: this works OK with Powershell instead of Windows Terminal. Haven't verified any other terminal emulators, but I'm pretty sure that it works OK in PuTTY as well. There are few bug tickets in other projects, like https://github.com/microsoft/WSL/issues/5931, but in my scenario it seems Windows Terminal is the culprit - hence the ticket here. Also for me this happens every time while in those other tickets it seems to happen randomly. TERM is `xterm-256colors` before starting tmux and `tmux-256colors` after starting tmux, both when using Windows Terminal and Powershell. And like in those other tickets I'm also using `set -s escape-time 0` in my .tmux.conf. Setting this to 50 solves the issue.
Author
Owner

@zadjii-msft commented on GitHub (Mar 28, 2022):

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #11204 for more discussion.

/dup #11204

@zadjii-msft commented on GitHub (Mar 28, 2022): Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #11204 for more discussion. /dup #11204
Author
Owner

@ghost commented on GitHub (Mar 28, 2022):

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 (Mar 28, 2022): 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.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#17075