Mastodawn

Well this is scary. Was coding some Go in neovim and noticed that some buffers for some reason had weird changes. Changes that I did not introduce.
Turns out something is very wrong and I cannot figure out the source of issue. Either LSP or something, but after some idle time some of the open buffer are garbled with edits.

And all this on fresh #neovim v0.12.1. Anyone seen something like this? Where to even start debugging this? #LSP config, #gopls?

Show thread

Kai 1d ago

@WindOfChange One way of debugging would be to turn off plugins one by one. When the buffer hickups stop, you have your culprit.

Show thread

Wind (Vējš)1d ago

@BonfireAtNight very tricky to reproduce. Even after disabling plugins I cannot be sure. Now I realise there may even be something else at play, like #ghostty . Chasing ghosts.

#neovim #phantomedits

Show thread

Kai 1d ago

@WindOfChange Not sure if you are on the right track there. How would a terminal emulator do edits inside a program?

I could be wrong, but I think this could happen only if it sent keypresses to the running application, and I don't see why it would do that.

Maybe you could try to program in Go without any plugins at all for an hour or so. I'm almost certain you won't have any technical issues.

Show thread

Wind (Vējš)

@BonfireAtNight well I am not aware of terminal internals. But I've seen many cases where terminal state gets garbled due to inconsistent client program behaviour, usually `reset` helps. But ofc, this is not a terminal program's fault. So, you are right - in this case it would still be an issue of neovim + some plugin.
Good thing I only have like 5 plugins.