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
broken tmux layout #7704
Comments
@luxifr - yes this is definitly same issue. |
apparently those question mark characters are
might be related to #6057 I also tried some tabby releases all the way back to version 143 to see if this might be some new regression but this issue has existed even in 143. |
@Eugeny if there's anything I can do to provide more info and to help solve this, please let me know... other than this issue I really love Tabby - it's heaps better than any of the other alternatives on Windows and I use it daily for work and personal stuff but this issue is really crippling... not for the cosmetic issues like in the |
same issue. |
Can you guys give this build a try? https://github.com/Eugeny/tabby/actions/runs/3838372546
|
Looks good for me so far with gnu screen. Will test more tonight. Well done! |
looking good!!! thanks man, you're awesome!
|
@Eugeny you have a new sponsor! |
Thank you! |
Hi, after extensive testing unfortunately problem is not fully solved. The isssue does not appear immediatly after opening a new tabby shell, but only after some time. Two problems:
|
I'm still getting this issue. if Tabby is left in a window with no activity the Tmux bar from the bottom just appends on top of it's self until it fills the screen. |
Describe the problem:
Special characters on tmux make my layout broken.
I can't replicate this problem on putty or 'Termius', also in 'Konsole' and 'gnome-terminal' probelem not appears.
Same problem on different versions of tmux and Debian.
Tmux versions with problems:
Screenshot ( with censored tmux content )
To Reproduce:
I using tabby instead of putty on my windows corporate laptop for connect to linux host from home.
The text was updated successfully, but these errors were encountered: