Post #3434319
2026-06-24 13:26 UTC
I updated neovim to 0.12.2 today, and it is completely broken. It deletes things I write, closes windows at random, goes to the next line when I `:w` and so many more bugs. It‘s the only thing I updated, and it worked completely fine before that. I‘m so angry, it is an essential tool for me and I‘m unable to work with this mess. I never had a vim or neovim update break anything in over 10 years. And now it is completely broken. For now, I will switch to vim, but I consider vim-classic and helix as the next step.
I can see no other reason for this than neovim adopting Claude et al heavily. It‘s the same story as rsync: A perfect track record, and now horrible bugs. I‘m sorry, but I really don‘t understand why stories like these keep happening, and people still think these tools are fine.
[Update: I ran it with no plugins and an empty config, the problems remain]
[Update 2: After some experimenting, I now figured out: It is the combination of the terminal emulator kitty (which is also adopting LLM-based development heavily 😒) and nvim >= 0.12.0]
Replies (4)
-
@stdevel@chaos.social 2026-06-24 13:28
@moonglum@yakshed.social Wow, didn’t know neovim also went down that trail. What an utterly mess.
-
@atax1a@infosec.exchange 2026-06-27 20:27
@moonglum@yakshed.social so sorry that you got double-slopped
-
@pedramardakani@fosstodon.org 2026-06-24 14:13
@moonglum@yakshed.social oh boy ... such tools going down the drain with AI slop ... that I do not like. I thought neovim contributors would be interested in the art of programming, rather than "generating" results 🤷 Looks like I got the wrong impression in the first place.
-
@okraits@mas.to 2026-06-24 14:39
@moonglum@yakshed.social By empty config you mean `--clean`?