- 2 months
Been using this for a long time now. I like my config to be minimal and this release doesn’t require much to do anything. I haven’t had a package manger, nvim-lspconfig and for a while I had no nvim-treesitter but that was more trouble than it was worth at the time. So my config is more like what you’d find in an IDE, setting up bindings and language support.
- 2 months
0.12 is probably close to the emacs experience, been a while since I used it. It’s all about being good out of the box.
- 2 months
Thanks for the hint. I was not aware of this before. Looking at https://neovim.io/roadmap/ and Prepare for version 1.0 #20451. Alright then it makes sense, as they are working towards specific goals to reach that state. Nice.
- 2 months
I tried neovim on windows. It is not quite the same experience. Especially neotree is very buggy
- spacemanspiffy@lemmy.worldEnglish2 months
I want to use it on my work PC (Windows) but its so slow its basically unusable. So I use VS with a Vim plugin.
- 2 months
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.
- spacemanspiffy@lemmy.worldEnglish2 months
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!
- 2 months
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. 😅

