3 ms·
TL;DR; neovim is garbage and the maintainers are arrogant. It’s a project that can’t die soon enough. If you’re actually proficient with vim and you’ve tried n
by vonwoodson 6y ago
TL;DR; neovim is garbage and the maintainers are arrogant. It’s a project that can’t die soon enough.
If you’re actually proficient with vim and you’ve tried neovim, than you know that the “shiny” is quickly overcome by the lack of core functions and system integration that makes vim a power tool to begin with.
If you want to use neovim, then you don’t understand what makes vim great in the first place. Here’s a hint: it’s not the key bindings.
And, the maintainers don’t care. They refuse to fix years-old bugs and feature requests. I believe it’s because they’ve painted themselves into a corner with their inexperience and lack of pragmatism.
Because it’s worth giving an example of its glaring mistakes, open up neovim in the terminal and “:!python” ... huh, doesn’t work ... that’s because neovim doesn’t have shell IO from processes it launches. When I googled the issue I found a feature request from 2013-ish. I can’t say anything now, because when I bumped the issue I was told that “ThIS ISn’T a cOre FeatURe, gvim diDn’T haVe THIs uNTil ...” and they closed the feature request at that. No fix, just a “f-u-very much” and the door. I had already posted a few other bug reports / feature requests, but promptly deleted them after that response. I’m done with neovim, except for recommendations that nobody use it.
Use real vim. Donate to help Uganda. https://iccf.nl/news.html https://iccf.nl/news.html
- dsissitka 6y agoI found your issue and that's not at all how it went down. I don't think they were the ones being arrogant. https://github.com/neovim/neovim/issues/1496 https://github.com/neovim/neovim/issues/1496 Edit: I missed the hidden comment the first time around. For those that can't log in: https://imgur.com/a/ysEiIkL https://imgur.com/a/ysEiIkL
- chrismorgan 6y agoI have never used NeoVim, but I am genuinely flabbergasted at the idea of not considering it a bug that :! is not interactive. I would consider that very close to fundamental functionality; I know that lacking it would make me stumble from time to time, and I’ve seen various other Vim users and plugins depend on it not irregularly also. I’m not confident I know just what’s meant by “gvim did not support this until 1-2 years ago”. Opening the command in a Vim terminal, sure, that’s recent functionality (as is the whole concept of a Vim terminal), and opt-in at that, but on MS-Windows at least, from time immemorial :! opened the command in a separate console window, meaning it always worked. Not sure what it does on other platforms, as I’ve long used terminal Vim exclusively. Also it sounds like they haven’t actually fixed this, just implemented the equivalent of Vim’s guioptions+=!, which… well, that’s definitely not how I want it to work.
- vonwoodson 6y agoOh yeah, that is my final reply to the thread on git, for sure. They are arrogant, and you’re welcome to not take my word for it. And, I will use continue real vim. Also, I will continue to disparage neovim. And, the issue still is not resolved. I will also continue to not give a fuck what they do.
- djoldman 6y agoI believe your example will be fixed in nvim 0.5: https://github.com/neovim/neovim/pull/10842 https://github.com/neovim/neovim/pull/10842