-
Notifications
You must be signed in to change notification settings - Fork 808
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
Strange characters appeared when entering Tmux #5931
Comments
And it happened in both my desktop and laptop. |
And it didn't happened in WSL 1. But my WSL 1 is Ubuntu 18.04. I'm not sure this is related to the Linux version or the WSL version. |
Ok, I finally resolved it. It happened when tmux run on Ubuntu 20.04. When your On Ubuntu 18.04, I add this line because there is a delay when I press So I just need to change the line to |
Thank you for reporting your solution! This fixed my issue as well, I was also seeing |
It helps! |
When entering with tmux 3.2+ w/ tmuxp, characters show: 0;10;1c microsoft/WSL#5931
Seems it works only for the first time start a Session, if you exit current session and run Originally posted by @roachsinai in tmux-plugins/tmux-sensible#61 (comment) |
For me only thing that fixed the characters appearing was placing |
prevents '0;10;1c' from being printed, cf. Fix: `microsoft/WSL#5931`
WezTerm would inject this version string into tmux as human-typed input: 0;10;1c>|WezTerm 20220408-101518-b908e2dd This would trigger my Alt+Shift+P shortcut in tmux, prompting for input. Pressing anything other than escape at this point would crash tmux 3.2a. This patch solves the problem by slowing down tmux's recognition of my escape key presses. See microsoft/WSL#5931
WezTerm would inject this version string into tmux as human-typed input: 0;10;1c>|WezTerm 20220408-101518-b908e2dd This would trigger my Alt+Shift+P shortcut in tmux, prompting for input. Pressing anything other than escape at this point would crash tmux 3.2a. This patch solves the problem by slowing down tmux's recognition of my escape key presses. See microsoft/WSL#5931
WezTerm would inject this version string into tmux as human-typed input: 0;10;1c>|WezTerm 20220408-101518-b908e2dd This would trigger my Alt+Shift+P shortcut in tmux, prompting for input. Pressing anything other than escape at this point would crash tmux 3.2a. This patch solves the problem by slowing down tmux's recognition of my escape key presses. See microsoft/WSL#5931
WezTerm would inject this version string into tmux as human-typed input: 0;10;1c>|WezTerm 20220408-101518-b908e2dd This would trigger my Alt+Shift+P shortcut in tmux, prompting for input. Pressing anything other than escape at this point would crash tmux 3.2a. This patch solves the problem by slowing down tmux's recognition of my escape key presses. See microsoft/WSL#5931
It seems like "tmux-sensible" plugins sets escape-time=0
|
Apparently the option in "sensible" is to avoid this issue, and the
Considering that, I think it would be advisable to set it as low as possible. I had the same problem as OP (with the exact same characters:
The weird character problem went away. Then when I set
The problem came back. So that's what's causing it, but I don't want to have a lag when leaving insert mode, so I set the following:
|
Przy starcie tmux pod WSL2 wyskakiwały znaki 0;10;1c Poprawka zgodnie z sugestią ze zgłoszenia microsoft/WSL#5931
Change escape-time from 0 to 1 (millisecond) to work around an issue on earlier versions of WSL: microsoft/WSL#5931 . This is imperceptible in vim and is the recommended solution in that issue. Signed-off-by: Rafael Kitover <[email protected]>
Thanks! I confirm that this solved the issue! 🙏🏼 |
For me any value other than 0 is working in below command:
I put above in .tmux.conf |
It's great that there's a work-around (and I will be using it), but did anyone try to root-cause and fix properly? |
Note: I never had this problem with KiTTY. I am only seeing it now that I am trying to switch to Alacritty. Due to flakiness of the network I work on, I get a good number of disconnect/reconnects. Each reconnect to tmux generates this string. So I see it constantly. And it is not just "terminal noise". It is registering as real keystrokes to bash. This is what I see after a weekend of not working. (I hit
|
- add session recover strategy for neovim ( not working )
Also started to see this issue... dont know why but when i start a when i removed the line |
change escape time to 1 to avoid extra escapes codes showing up in wsl (microsoft/WSL#5931)
for anyone having it not work, place the set -s escape-time 1 line after the tmux sensible line. |
it happens to me after upgraded Ubuntu (V22). nothing above works for me. |
A related question similar to this was answered here: https://serverfault.com/a/1130091/481120. Here's the relevant part of the answer:
|
|
Thanks man, it works for me! |
I know this is absurd and that this solution will give a loading error, but it was the only thing that made the strange characters not appear
I'm using manjaro i3 with urxvt terminal |
Environment
Steps to reproduce
tmux new -s test
, then enter the session.tmux attach -t test
Expected behavior
no strange characters
Actual behavior
There are some strange characters appeared before the cursor. They are
0;10;1c
. Like this:But it didn't always happen. This is a chance event.
The text was updated successfully, but these errors were encountered: