fredizzimo

I'm pretty sure that this was fixed by: * https://github.com/neovide/neovide/pull/2012 And released in Neovide 0.11.2. There was also another similar fix released in 0.13.0: * https://github.com/neovide/neovide/pull/2298

This is either some regression in Neovim nighly or some new event we don't handle. I will take a look at it soon, but do you remember when you last...

Unfortunately. I can't reproduce this here, it's probably caused by some plugin, can you try to run `neovide -- --clean` and see if it happens?

Most likely the `nvim-treesitter-context` plugin, I will try to install that here. That's not it, at least not for me.

It looks like some of the data we get from Neovim might be lost on the way. The response we get for `nvim_input` is not supposed to be `{"kind": "syntax",...

@CertainLach, thanks, is that plugin enough to reproduce the issue? If you follow this: https://github.com/neovim/neovim/blob/master/contrib/minimal.lua, If you prefer you can alternatively create a single file `lazy.nvim` configuration that can be...

I tried to reproduce this again, but I didn't manage to with the latest version of https://github.com/lewis6991/hover.nvim and neovim nightly. So, it would be good to get a full configuration...

Maybe it's not a plugin. I have quite strong hunch that this might be doing something wrong * https://github.com/neovim/neovim/pull/27655 It seem to do so in the terminal mode: * https://github.com/neovim/neovim/issues/27859...

Thanks, I reported our findings here: https://github.com/neovim/neovim/issues/27859#issuecomment-2044764163

Can you all test with the latest Neovim nightly build from today? There's another potential fix here * https://github.com/neovim/neovim/pull/28717