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 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!