microsoft / microsoft/terminal
tmux exception in windows terminal
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 105k
- Forks
- 9.6k
- Avg merge
- 3d 17h
- Merged PRs (30d)
- 29
Description
### 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](https://github.com/tmux/tmux/issues/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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue by connecting from Windows Terminal to the openSUSE VM over SSH and running tmux, then compare the behavior with PuTTY or MobaXterm. Start by investigating the terminal behavior associated with tmux issue #2844; done means the `^[[>0;10;1c;` sequence is no longer printed in Windows Terminal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100