85
Neovim 0.12.0 released
(github.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 29 Mar 2026
85 points (97.8% liked)
Programming
26499 readers
143 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
I experienced the same bug in winslop: It is not the neovim fault, but the terminal emulator. While WT (default for 11) is good enough, for some computers it is pretty laggy. I recommend wezterm.
Source: I manage many onprem windows PCs with automation, and some 1 of them experienced this issue.
Whoa you weren't kidding! It still chugs in our large project, and I have some Windows issues in my config to fix, but nvim itself runs well for me now!
I am happy that I've been useful ๐ The experience on windows will always be worse than on linux sadly. But I have no choice, I have to use winslop for work, so I made it work. ๐
I may try this. Thank you for the tip!