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
By empty config you mean `--clean`?
@okraits I tried both: Deleting everything in my init.lua, and —clean. The result is the same.
@moonglum So when you have a file open in a buffer, and you save it with `:w`, then the cursor goes down one line in the buffer?
@okraits Yes, that‘s one of the bugs 👍 Completely reproducible, happens every time.
@moonglum I thought I could reproduce it with
https://github.com/neovim/neovim/releases/download/v0.12.2/nvim-linux-x86_64.appimage
but it doesn't happen here.
Does it happen for you with the appimage?
@okraits I can even reproduce it in a container:
podman run --rm -it alpine
nvim --version # 0.12.2
apk add neovim
nvim
=> this bug, as well as some of the other bugs are there. (Also works with docker)
@moonglum And with the appimage I was using as well?
@okraits Yep, that app image has the same issues 🙈
@okraits I now also downloaded the 0.12.3 version as an app image, same issues
@moonglum That's really strange that it doesn't happen to me with the same appimages.
Can you give another example of a concrete bug which I can try to reproduce?
@okraits The bugs happen 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 Debian in containers (both < 0.12), where it does not happen. So it is definitely the update (and as I‘m using no config, it can’t be my neovim config or a plugin either).
The other bug I see immeaditely: in insert mode, it inserts an empty line after each line I add. And when I do :e and go up and down the list, it always skips an entry. As I said: It is completely broken.
@moonglum
I can't reproduce those issues if I understood them correctly.
But it sounds like an additional Return keypress is sent to the editor. Could it be related to the terminal emulator or a terminal multiplexer you're using?
@okraits I don‘t use a multiplexer and my terminal emulator is kitty. You might be right, it could be kitty + nvim 0.12 👍 I will try it tomorrow, I closed my computer for the day.
(But, still, it must be caused by a change in nvim, as it works fine with kitty + nvim 0.10 and 0.11)
Thanks!
@moonglum Good luck - would be nice if you would get it sorted out.
You're welcome, I'm happy to help.
Lucas Dohmen
Oliver Kraitschy