Live data from Hacker News

NeoVim 0.2.0 released

github.com

41–50 of 141 posts

Re: NeoVim 0.2.0 released

#41

Earlier quoted context omitted.

Some distros do have it in the official repos https://github.com/neovim/neovim/wiki/Installing-Neovim

Yes, but it is not installed as the default text editor. Unlike vi/vim/nano

The default is usually vi or nano, not full vim. So installing vim or neovim should take about the same effort.

Re: NeoVim 0.2.0 released

#42
post #24

I understand why they started neovim, but don't think the split between vim 8 of today and neovim is a good thing. Makes me think of emacs vs xemacs but worth because they use slightly different dialects of vimscript (closures, currying in vim 8, different api for asynchronous calls). I personally wish they'd meet on some common, standardized ground. This would require both parties to accept they are not alone though…

> I personally wish they'd meet on some common, standardized ground. This would require both parties to accept they are not alone though. Yeah, not going to happen. ViM's author is remarkably hostile to the efforts of NeoVim and the ideas it brings forth.

Can you back up this claim? I think it's not true and authors of both projects respect each other. They simply have different views regarding backwards compatibility etc.

Re: NeoVim 0.2.0 released

#43
post #35
post #25

Earlier quoted context omitted.

Honestly for me the main reason was that it finally has builtin `:terminal`. The plugins for use with vim have always been slightly buggy for me.

Can you please elaborate how you make use of the built in terminal emulation of neovim? Whenever I see a mention I think "neat" but have yet to integrate it into my workflow.

Not parent, but I use Neovim and Ranger [1] filemanager and I have a shortcut to open Ranger in a split or full window from which I can browse and open a file. You can do this only because Neovim has a built-in terminal. This may end up replacing vinegar [2] as my in-VIM filemanager.

[1] https://github.com/ranger/ranger

[2] https://github.com/tpope/vim-vinegar

Re: NeoVim 0.2.0 released

#44

Earlier quoted context omitted.

Yes, but it is not installed as the default text editor. Unlike vi/vim/nano

The default is usually vi or nano, not full vim. So installing vim or neovim should take about the same effort.

In what distros? Ubuntu comes with vim.

Re: NeoVim 0.2.0 released

#45

I understand why they started neovim, but don't think the split between vim 8 of today and neovim is a good thing. Makes me think of emacs vs xemacs but worth because they use slightly different dialects of vimscript (closures, currying in vim 8, different api for asynchronous calls). I personally wish they'd meet on some common, standardized ground. This would require both parties to accept they are not alone though…

The diffwrence in performance is hhuuuugggee! Vim lags on my project, nvim doesnt! Quadcorei5, 16hb ram!

That's strange. Do you have some unusual plugins?

Re: NeoVim 0.2.0 released

#46
post #4

I'm currently using vim and I'm quite happy with it. I don't use many plugins, so better support for plugins is not very helpful to me. Are there other reasons why I should switch to Neovim?

Had the same question since I just started with vim.

What I saw in using nvim:

    - terminal use
    - async plugins
    - it's almost entirely compatible to vim anyway, so you can switch whenever you want to.
Also would like to say thanks to the devs working on making neovim.

Re: NeoVim 0.2.0 released

#47
post #5

Hope someone (not me!) starts working on a nvimclient (akin to emacsclient) soon.

maybe neovim-remote is what you want? https://github.com/mhinz/neovim-remote

Close, but not enough. I want to open the same editor session spread across multiple windows on multiple monitors.

Re: NeoVim 0.2.0 released

#48
post #23

I have been using Vim as my primary editor for many years and am happy with it. People I know who use developer editors are split between Vim and Emacs. Neovim usage is minimal. Why? It is an honest question. I see developers of the editor happy, which is a good thing, but IMO to get more users NV must show why it is better from a user perspective -- have several demos on the powerful things easily achieved with NV t…

Without neovim, vim wouldn't have gotten the async features. The fact that it's a community driven project and not dictated by one single BDFL makes it a lot more sympathetic for me.

Vim is also community driven. Having a BDFL doesn't mean that the model is bad. Python, Linux all have BDFLs and they are blossoming.

Also, saying that Vim wouldn't have gotten the async features without Neovim is wrong. It would have come in sooner or later, Neovim sure made it a priority.

Re: NeoVim 0.2.0 released

#49
post #27

I use Neovim on daily basis. It works really well. It requires tremendous efforts and love to transform a huge archaic code base into a much modern one. Thanks, Neovim team!

This can be said for any rewrite. Let's wait and see what happens to Neovim's code in coming 10-15 years if it can last that long. When you have to support all the legacy systems and all types of OSes out there, crap is going to come in the code.

Re: NeoVim 0.2.0 released

#50
post #42
post #24

Earlier quoted context omitted.

> I personally wish they'd meet on some common, standardized ground. This would require both parties to accept they are not alone though. Yeah, not going to happen. ViM's author is remarkably hostile to the efforts of NeoVim and the ideas it brings forth.

Can you back up this claim? I think it's not true and authors of both projects respect each other. They simply have different views regarding backwards compatibility etc.

I think 'hostile' is a bit harsh. I'd say 'infinitely reticent to large changes'. All the neovim authors wanted, was a list of blockers needed to merge their async patch. Bram would never give them that, always coming up with one more change. I've seen this pattern of infinite reluctance before, especially when communities depend heavily on one maintainer. its not about async and the specific semantics of the patch after a certain amount of time, it's about deeper issues like project vision, control, and perhaps trust. https://groups.google.com/forum/m/#!topic/vim_dev/-4pqDJfHCs... https://geoff.greer.fm/2015/01/15/why-neovim-is-better-than-...,
Post reply on HN