News for hackers. Stuff that matters.
Re:Why neovim is better than vim (2015) by blackbrokkoli on Sunday August 05, 2018 @07:22AM (#17690775)
It should be mentioned that the author has very strong conflict of interest.

Also, isn't the appeal of vim that it's universal rather than that it's beautifully coded? I don't have the expertise to care about weird indentation in source code personally but I like that the text editor I have on my daily-use machine is probably also accessible on a 80's-era server on the other side of the world...

Re:Why neovim is better than vim (2015) by Justsignedup on Sunday August 05, 2018 @09:12PM (#17694517)
Vim being universal is pretty meh. Try using vanilla vim, you'd hate it after using non-vanilla for a while. It is like a whole different world.

At that point why not just use sublime or w/e.

Re:Why neovim is better than vim (2015) by seanhunter on Sunday August 05, 2018 @11:33AM (#17691813)
I have changed over to neovim for most of my editing, but the one thing I have found is that it seems much slower to start up. Pretty sure this is a bug they'll fix soon, and other than that it's really pretty great. I don't actually use the Terminal window feature, but there are a few things about it that I like: 1)Decent python2 and 3 support (yes both at the same time) 2)Getting the * and + registers to actually work seems less annoying than in regular vim (ymmv at least I don't have to rebuild neovim from source to get these). (check out :he quoteplus and :he quotestar if you don't know - these are awesome)
Re:Why neovim is better than vim (2015) by nicolashahn on Sunday August 05, 2018 @09:27AM (#17691212)
Author claims that vanilla vim would never support async linters, but that's changed now: https://github.com/w0rp/ale
Re:Why neovim is better than vim (2015) by hayd on Sunday August 05, 2018 @02:11PM (#17692614)
Would it exist in vim without neovim. The landscape has changed, but part of that is due to neovim's existence.
Re:Why neovim is better than vim (2015) by icc97 on Monday August 06, 2018 @09:02AM (#17697170)
Also neomake (https://github.com/neomake/neomake) is supported in Vim 7.4+ too, with the async features available from v8+
Re:Why neovim is better than vim (2015) by vr46 on Sunday August 05, 2018 @04:28PM (#17693358)
Have used Neovim exclusively for a few years now and I can’t say I need to switch back. It is Vim now.
Re:Why neovim is better than vim (2015) by proginthebox on Monday August 06, 2018 @03:35AM (#17695786)
how do you integrate neovim clipboard with system one? I use KDE/X11 although I do not think that should be relevant.
Re:Why neovim is better than vim (2015) by jvanderbot on Monday August 06, 2018 @10:38AM (#17697947)
I just pipe lines to xsel. Not elegant, but works.