Live data from Hacker News

NeoVim 0.2.0 released

github.com

91–100 of 141 posts

Re: NeoVim 0.2.0 released

#91
post #83
post #8

Major version can make someone think nvim is still unstable. My experience is the opposite. I have being using it for 2-4 years (can't remember exactly) and got the same 0 problems I run into Vim. Earlier versions required you to recompile NeoVim to enable new features for plugins. Yesterday I installed NeoVim in my new laptop and it was a smooth experience: Installed it using Ubuntu package manager, installed Vim-Pl…

I tried jumping boat to nvim something like a year ago. One of my plugins ran into an issue, so I came back. A better question for us "old-vimers" is not "is nvim stable, because I'd like something modernized", but rather "what does nvim have that vim doesnt". I'm actually asking. My short glance led me to believe that it's got two things going for it: a) smoother interop with other "modern" tools b) cleaned up codeb…

The major reason I use neovim is because with the addition of :terminal command I no longer need to remember tmux commands and with the add-on neoterm I have a one button command to send the current selection (or line) to whatever terminal I please.

This means that when developing code in any language that has a REPL I can test it out as I develop line by line.

Re: NeoVim 0.2.0 released

#92
post #52
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?

Faster startup, mouse works as you'd expect in a regular desktop app. Switch panes, tabs, open new tab, scroll panes, resize panes, select ranges, all in the terminal. I know not using the mouse is one of the reasons why one would choose vim, but the mouse really is faster/more intuitive in some situations.

The mouse features you describe are already available in regular vim; I have been using them since long before NeoVim existed. Are they improved somehow?

Re: NeoVim 0.2.0 released

#93

Earlier quoted context omitted.

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.

To be fair, supporting all legacy systems and all types of OSes seems to be an explicit non-goal of neovim.

Neovim does have breaking changes from Vim, that by definition make support for some of these systems very hard or impossible.

Re: NeoVim 0.2.0 released

#94

Earlier quoted context omitted.

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.

The main reason NeoVim exists at all is because Bram Moolenaar refused to accept any patches for async support. People already did the work for him and he didn't want it. So they decided to write their own text editor that supported async plugins. Bram got butthurt and didn't want to lose a large portion of his user base, so he added async support. NeoVim's first public release (version 0.1) was released in December…

> The main reason NeoVim exists at all is because Bram Moolenaar refused to accept any patches for async support. People already did the work for him and he didn't want it.

This is not true. If the work was not complete and not as how the lead maintainer/developer wants it. It is highly unlikely that it would be merged. I suggest you actually go and read the mailing list when this happened. I have seen it.

Re: NeoVim 0.2.0 released

#96

Earlier quoted context omitted.

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.

The main reason NeoVim exists at all is because Bram Moolenaar refused to accept any patches for async support. People already did the work for him and he didn't want it. So they decided to write their own text editor that supported async plugins. Bram got butthurt and didn't want to lose a large portion of his user base, so he added async support. NeoVim's first public release (version 0.1) was released in December…

Also, I like Neovim and have been using it on/off since a couple of years. But I haven't found a GUI equivalent of Macvim with Neovim.

Re: NeoVim 0.2.0 released

#97

Any reports on how stable the Windows release is?

I don't know if it'an issue on my side, but I have not manage to do anything with the :terminal on Windows 7. It starts a prompt but I can not input anything in Terminal mode. I tried 'i' to go in insert mode in the terminal but it does not seem to work either. (To be sure this is not something in my vimrc, I tried with and without it). At that point I am not sure if this is a problem between chair and keyboard or a bug.

Re: NeoVim 0.2.0 released

#98

Earlier quoted context omitted.

It's not about elitism, it's about using the tool you've chosen efficiently. If I used the IDEs you use, and you suggested to me a way of using them more efficiently, I wouldn't accuse you of elitism. I'd thank you for showing me something new and improving the way I work. Have you ever witnessed somebody using a mouse to move between form fields? My bet is you at least thought about telling them they can use the tab…

If I told them they didn't really know how to use a browser because... they didn't know to use tab to move between fields... I wouldn't be surprised in the slightest if they came back with some comment about the subtle elitism

Ha, fair enough. But that really only shows that my example wasn't great.

If you eat soup with a fork, you don't know how to use silverware. If you drive nails with a ball-peen hammer, you don't know how to use hammers. That's not hammer or silverware elitism.

IMO, using a mouse in vim shows that you don't know vim. You can still get the job done, but why not commit to using the tool as intended?

Re: NeoVim 0.2.0 released

#99
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…

The simple answer is probably the correct one. It's not included by default in any distributions.

It's in the official repos for many distros including OpenSUSE.

I actually am fixing up the install documents even though I don't use Neovim

Re: NeoVim 0.2.0 released

#100
post #43
post #35

Earlier quoted context omitted.

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

So the nesting you have is Shell -> Nvim -> Ranger, so ranger is contained inside of a vim split?

Mind sharing some docs on how to do that?

Post reply on HN