3 ms·

>None of the ones that support macOS are good, and all of them that don’t have explicit macOS support are all awful. VimR is very good; I've been using it befo

>None of the ones that support macOS are good, and all of them that don’t have explicit macOS support are all awful. VimR is very good; I've been using it before it started using Neovim as the core [1]. [1]: https://github.com/qvacua/vimr https://github.com/qvacua/vimr

halostatue 4y ago
It’s not very good. It is perhaps the best available Neovim GUI, but VimR has been an unusable mess every time I have tried because it’s trying to be an IDE first and not Vim first. Before I can take Neovim seriously, I need a Neovim GUI that is exactly what gvim or MacVim provide — not something that adds features I neither want nor need nor can I easily disable. Granted, it’s been about six months since I’ve used VimR, but I bounce off it every time, because it doesn’t work with the configuration that I have built up trying to match my Vim configuration to the best of my ability.
- alwillis 4y ago
  >Before I can take Neovim seriously, I need a Neovim GUI that is exactly what gvim or MacVim provide — not something that adds features I neither want nor need nor can I easily disable. Having used MacVim for several years and now using Neovim mostly in the terminal but sometimes VimR, I disagree that it's a mess. I get wanting to have a common gvim ui/ux across platforms, but I think having a Mac-like or Windows-like ui/ux on those platforms mostly trumps that. Also, the special features of VimR, like the built-in file browser and Markdown preview can easily be disabled. Using the native rendering of macOS and support for ligatures, for example, is certainly a plus IMHO.