4 ms·

I've been using neovim for maybe 6 months now, but as of yesterday I'm gonna switch back. First, I was shocked that they changed the behavior of Y. That was ba

I've been using neovim for maybe 6 months now, but as of yesterday I'm gonna switch back. First, I was shocked that they changed the behavior of Y. That was bananas to me. But I discovered that really early on and powered through. What's making me move back is I just opened a huge CSV file in vimr, and it hung forever. Usually you can ^C to make vim quit counting lines, but no dice. That's a non-starter for me, unfortunately. I was really into the Lua support, but so be it.

musaeus 4y ago
> What's making me move back is I just opened a huge CSV file in vimr, and it hung forever Isn't this an issue with VimR and not NeoVim? I've used terminal NeoVim since it started and literally never had it choke on anything, ever. VimR is just a GUI wrapper, and while a neat project, it has tons of problems.
- camgunz 4y ago
  Well, I guess this is also under the umbrella of "why I'm switching back": GUI clients are kind of a mixed bag. Mostly, their colors are oversaturated and are unmaintained: neovide: colors oversaturated and seemingly always antialiases, even when you try and turn it off [0]. It also crashes on "set guifont=ProggySquare:h11". goneovim: colors oversaturated neovim-qt: colors oversaturated gnvim: looks unmaintained, no macos package (probably easy to build, but why) neovim-gtk: looks unmaintained [0]: https://github.com/neovide/neovide/issues/1102 https://github.com/neovide/neovide/issues/1102