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]
perf(completers): use DirEntry::file_type() instead of metadata() (#1… · helix-editor/helix@22d0d29

…5433) `DirEntry::file_type()` uses the `d_type` field from `readdir` on Linux, avoiding a per-entry `lstat` syscall that `DirEntry::metadata()` requires. Behavior is unchanged as both return syml...

GitHub
@fogti Sigh, thanks for the hint 🥲
@fogti Seems to be that single commit, from what I see:
https://slopscan.ava.pet/repo/https%3A%2F%2Fgithub%2Ecom%2Fhelix%2Deditor%2Fhelix

That‘s definitely a different level than what is happening in vim/neovim. I will keep that in mind though – thanks!
https://github.com/helix-editor/helix

@moonglum @fogti A single commit from a contributor with no other commits, so yeah, seems fine