-
Notifications
You must be signed in to change notification settings - Fork 499
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
Inconsistent with terminal of vim.fn.screen* function #2569
Comments
I think this might be related to this bug we reported to Neovim a while ago: Does it work properly if you jump using the keyboard? |
Yes, mouse and keyboard is the same, and row and col is correct, only char is wrong |
I assume that you have tested this in the Neovim terminal app? It sounds strange that this is brokens, since Neovide does not manipulate any screen and cursor positions itself. |
Yes, kitty print correct cursor char |
Just wanted to chime in that I think I ran into this or a similar bug while I was trying to debug an issue I was having with the statuscol plugin. It uses What I managed to figure out so far is that for some reason
on this test file:
This is what I get in nvim running inside a terminal: And this is what I got when I ran it inside neovide: Starting neovide with I have the same setup as @xzbdmw btw, MacOS Sonoma 14.5, nvim 0.10 stable and neovide 0.13.1, terminal is alacritty. I've had this issue since I started using the statuscol plugin (around neovide version 0.10 or 0.11) but I only very recently noticed that I can't reproduce it in the terminal. |
I reported a Neovim issue here: |
Describe the bug
vim.fn.screen* function only return statusline result
To Reproduce
Steps to reproduce the behavior:
repro.lua
move cursor to a char and type gt, the result is random string from statusline
Expected behavior
the result should be the same as cursor char
Desktop (please complete the following information):
macos 14.1
neovim 0.10 stable
neovide 13.0
Please run
neovide --log
and paste the contents of the.log
file created in the current directory here:neovide_rCURRENT.log.zip
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: