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]

@moonglum Running 0.12.2 on my work laptop 8 hours a day and didn't saw a single bug until now. I even can't reproduce your ":w changes the line", neither locally nor with your alpine setup further down the thread.

I don't want to play devils advocate for vibecoding but apparently even your simplest example is not that easy to reproduce.

@fleaz So what you‘re saying is…? It happens reproducible on my machine for 0.12.2 (Alpine and App Image) and 0.12.3 (App Image). I just tried it with an older Alpine and stable Debian in containers (both < 0.12), where it does not happen. So…?

@moonglum What im saying is: If it only happens on your machine, and not on my machine, this bugs depends on a specific condition (whatever it is) and does not happen 100% of the time.

Therefore the devs maybe also didn't saw it.

@fleaz Yep, applications like vim, neovim, bash… run on macOS, all kinds of flavors of Linux, *BSDs… for centuries. Nothing about that has changed.