-
Notifications
You must be signed in to change notification settings - Fork 743
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
Screen corruption with neovim #1041
Comments
SCRIPTFILE.txt |
I’ve also been having similar screen corruption issues in neovim. At this point I’ve spent a couple of hours cumulatively trying to fix this, and I finally have a (hackish) workaround. On my server’s
When using Despite this workaround, I’d really prefer if mosh natively solved this. |
I've also been having this problem, but
It would be nice if mosh was able to handle these sequences more gracefully if it's going to set |
Mosh supports C1 controls, but is locked to Unicode only -- it doesn't support ISO 2022 charset-switching sequences on purpose. (See #1127 (comment) for a longer rationale.) neovim should be using Unicode (ISO 10646) characters when the terminal charset is Unicode and NCURSES_NO_UTF8_ACS is set, rather than ISO 2022 locking shifts into an alternate charset. |
@keithw thanks for your explanation, but how can I found out which char/icon in my neovim config file or in my neovim plugin file incur this corruption. |
So this means it wont get fixed ? Neovim is one of the most important terminal programs out there. |
Just to show how nasty this corruption can get. Scenarios like this render it basically unusable. https://youtu.be/4ySMoZWfEgM |
I get the same kind of corruption @ProducerMatt. Both vim and emacs. |
This issue disappears when I disable lualine.nvim, and consistently reproduces when I re-enable lualine. Maybe some characters or escape sequences from lualine has been causing the issue? Can the other commenters share whether you are using lualine (or some other *line plugins)? Found a related issue in the lualine repo: Bug: when running mosh with neovim and lualine, terminal is broken #1199 |
I wasn't using a *line plugin back when I was using mosh and encountered this issue, so the problem isn't specific to those |
I apologize for resurrecting this old issue and adding a seemingly unhelpful '+1', but I'm glad to know I'm not alone in experiencing this problem. For years, I've been plagued by randomly broken characters in neovim, but I had no idea what was the cause, so it became a 'normal' part of my neovim experience. And today, just before finding this issue, I discovered that the problem only occurs with mosh connections, not with ssh connections or local terminals. While I can work via ssh or locally for now, I'd be really happy it if it could be resolved. |
Screenshot with mosh
Screenshot with ssh
I’m running mosh server built from master on Amazon Linux AMI. For a client, I’ve used iOS apps “blink” and “termius”. I can reproduce above results stably on both of the clients — note that how the start of a 3rd wrapped line is dedented.
Maybe it is a bug of my configuration, if so any help on the configuration would be appreciated.
The text was updated successfully, but these errors were encountered: