Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
gurka opened this issue Mar 24, 2022 · 3 comments
Closed
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@gurka
Copy link

gurka commented 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
@gurka gurka added the Issue-Bug It either shouldn't be doing this or needs an investigation. label Mar 24, 2022
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Mar 24, 2022
@gurka
Copy link
Author

gurka commented 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 microsoft/WSL#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.

@zadjii-msft
Copy link
Member

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

@ghost
Copy link

ghost commented 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 ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Mar 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants