-
-
Notifications
You must be signed in to change notification settings - Fork 6k
Unexpected character after update #5990
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
Comments
That's probably due to ef753a7. If you put |
Yes, your terminal should ignore unknown sequences. |
@dikiaap What does |
@justinmk Already fixed this. I did |
libvte-2.19-0 Version 0.42.5-1ubuntu1 |
Just wondering, why has this been marked closed? Is |
@kantsdog It's not that simple. Terminals have all kinds of brokenness, and this is one of them. Many support changing the cursor shape, but do it in one of two different ways. And while there are ways to query whether or not a terminal supports the feature, most do not implement the mechanism. So we're stuck with user configuration until the situation improves. :-( |
I made a change that enables cursor shape by default. It looks like the state of terminals having even basic fallback behavior is worse than expected, so I'll switch it back to opt-in instead of opt-out. I guess querying will be the only way this can be automatically enabled, because of all the broken terminals out there. (I'm grateful for the feedback from users giving us early warning about this) |
@justinmk Thanks for changing it back to the default. Had I not found the solution in this thread, Neovim would have become unworkable for me and people in my situation, so switching it back to opt-in seems like a good call from my perspective. @jszakmeister Thanks for the helpful and informative explanation of terminals in all their brokenness. |
Thank you very much. I have also realized that unsetting TERM when calling nvim does also "fix" this issue. |
@prlz77 Unsetting TERM is a very heavy-handed approach to "fix" this. Just add |
@jamessan I changed it when I discovered this thread. Thank you anyway! |
@jamessan It worked as you suggested. Thank you!. |
User can still set guicursor explicitly in init.vim. Closes neovim#5990 Closes neovim#6403
User can still set guicursor explicitly in init.vim. Closes neovim#5990 Closes neovim#6403
Thank you, the problem persisted even with I solved it with |
@tarciozemel #6997 should address your issue when it's merged soon. |
Also solved my problem with |
Question about this issue: Is it likely to be fixed in time, without users having to specify some variable like I've updated my NeoVim time and time again hoping it would be fixed, but maybe I am waiting for naught and there is no way it's simply going to work without having to set some variable? (What does |
The similar situation only occurs when I use 'sudo'. If I use nvim normally, everythin is ok. But if I use nvim with 'sudo' , changing mode(such as 'inserting mode, command mode) comes with a unexpected char 'q' (only one character 'q'). Is this the same as the problem you've disscused above? |
@ydajwz123 sudo changes your environment and the loaded config so it can be several things. You can |
@teto thanks, now I have a better understanding of how it working. |
@kabasakalis $NVIM_TUI_ENABLE_CURSOR_SHAPE got removed a year ago (bootom of https://github.com/neovim/neovim/wiki/Following-HEAD) |
@teto Right, I don't have time to follow the changelog. And I noticed you already mentioned guicursor in a comment above, so I am deleting my comment. |
I also have the problem on Terminator and tmux. I had set the VTE_VERSION on my init.vim and fixed the problem:
|
nvm --version
: NVIM 0.2.0-dev$TERM
: xterm-256colorI was updating neovim and this character suddenly appear. Before updating, this isn't happen.
Tested in vim, all is fine.
The text was updated successfully, but these errors were encountered: