4 ms·
I 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:
by dsissitka 6y ago
I 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.