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 rsync as wel??
Jeremiah Fieldhaven (@[email protected])

So my systems recently updated to rsync 3.4.3, and as soon as that happened my backup system - which does incremental backups using multiple --compare-dest= arguments - started to fail on anything but a full backup. Revert to 3.4.1 and it works. So I go look at the source in GitHub to see what might have changed, because there doesn't seem to be anything relevant in the changelog. Since 3.4.1, 36 commits by "tridge and claude" Oh for fuck's sakes.

Gamedev Mastodon
rsync and outrage

I gave up blogging a long time ago (apart from an occasional thing about ArduPilot), I tend to just write code and hope people find it…

Medium