Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

NeoVim 0.2.0 released

github.com

Post reply on HN
Print view View original

71–80 of 141 posts

Re: NeoVim 0.2.0 released

#71

Post by isthisnagee »

lucky_cloud wrote: post #63
monzee wrote: post #52

Earlier quoted context omitted.

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.

Using a mouse is not faster if you really know how to use vim. I guarantee I can get to any line in any window in any tab faster than it takes for my hand to even reach the mouse. Same for resizing splits, selecting ranges, whatever. It's only more intuitive if you're stuck in a GUI mental model. Disable mouse support and learn to navigate vim just like you learned to edit in vim. Not trying to come off as confrontat…

Resizing panes is more intuitive with a mouse imo. Doing it with a command just leaves me guessing and estimating how much to move things.

Re: NeoVim 0.2.0 released

#72

Post by BoorishBears »

lucky_cloud wrote: post #63
monzee wrote: post #52

Earlier quoted context omitted.

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.

Using a mouse is not faster if you really know how to use vim. I guarantee I can get to any line in any window in any tab faster than it takes for my hand to even reach the mouse. Same for resizing splits, selecting ranges, whatever. It's only more intuitive if you're stuck in a GUI mental model. Disable mouse support and learn to navigate vim just like you learned to edit in vim. Not trying to come off as confrontat…

Being "stuck in a GUI mental model" means I use IDEs for most development I do instead of vim/emacs (which I guess would be the extreme of being stuck in that model?). At the end of the day using my mouse to open a file doesn't impede my ability to code in the slightest.

I've never understood the almost subtle elitism behind being able to use Vim without a mouse because "moving your hand to the mouse is slow". If a problem is so simple my writing/editing a solution for it is constrained by... the time it takes my hand to move to my mouse... I usually just fire up nano.

Re: NeoVim 0.2.0 released

#73

Post by lunixbochs »

This release fixes one of the biggest bugs with asynchronously embedding Neovim (some input states would just block the API), and makes ActualVim more reliable as a result. Neovim embedding works pretty well now, and will only get better. I'm hoping it will be possible soon to embed the entire Vim experience into another editor with little to no tradeoffs on either side. I've been impressed when interacting with the Neovim developers.

Re: NeoVim 0.2.0 released

#74

Post by cookiecaper »

executesorder66 wrote: post #54
mundanevoice wrote: post #48

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…

Yes, competition is very healthy and good for an ecosystem overall. Though the entire sector my business operated in eventually got shut down due to unscrupulous competitors, can't deny that competitors really lit a fire under my butt compared to the first year, when I was in the field alone.

Re: NeoVim 0.2.0 released

#76

Post by dmix »

lunixbochs wrote: post #73

This release fixes one of the biggest bugs with asynchronously embedding Neovim (some input states would just block the API), and makes ActualVim more reliable as a result. Neovim embedding works pretty well now, and will only get better. I'm hoping it will be possible soon to embed the entire Vim experience into another editor with little to no tradeoffs on either side. I've been impressed when interacting with the…

Neat, for those unfamiliar as I was:

> Actual uses an embedded Neovim instance to accurately manipulate each Sublime Text buffer as though you were editing the text directly in vim, without breaking any Sublime Text features (aside from multiple selection for now).

https://github.com/lunixbochs/actualvim

Re: NeoVim 0.2.0 released

#77

Post by lunixbochs »

dmix wrote: post #76
lunixbochs wrote: post #73

This release fixes one of the biggest bugs with asynchronously embedding Neovim (some input states would just block the API), and makes ActualVim more reliable as a result. Neovim embedding works pretty well now, and will only get better. I'm hoping it will be possible soon to embed the entire Vim experience into another editor with little to no tradeoffs on either side. I've been impressed when interacting with the…

Neat, for those unfamiliar as I was: > Actual uses an embedded Neovim instance to accurately manipulate each Sublime Text buffer as though you were editing the text directly in vim, without breaking any Sublime Text features (aside from multiple selection for now). https://github.com/lunixbochs/actualvim

That needs amending:

- It also breaks the automatic (while typing) completion and snippet suggestion popups (though Sublime's autocomplete has been wired into Vim and works great there)

- Sublime's undo works but isn't coalesced properly while you're in Vim mode (but Vim's works fine there).

Re: NeoVim 0.2.0 released

#78

Post by nolliebs180 »

ptero wrote: 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…

I am a developer using vim & neovim daily. My setup before VM/container popularity was mostly ssh into a remote dev box, then tmux+vim there on the remote host. Tmux mostly for its split-pane feature which I like better than vim splits.

Now since I can do most of my work locally, neovim's terminal support has, for me, completely replaced my use of tmux splits. Having moved all my split usage out of tmux into neovim has simplified my setup and keybindings. And I grok and am more comfortable now with vim/neovim splits.

Re: NeoVim 0.2.0 released

#79

Post by gh02t »

cryptarch wrote: post #57
vopi wrote: post #44

Earlier quoted context omitted.

In what distros? Ubuntu comes with vim.

Debian Stable (without a DE) only comes with nano AFAIK.

It has vi in the base system, specifically `vim-tiny`. Vi is mandated by POSIX, so pretty much every distro includes some minimal version of it in the base system. `nvi` is also used sometimes instead.

Re: NeoVim 0.2.0 released

#80

Post by Trd »

baldfat wrote: post #64
executesorder66 wrote: post #54

Earlier quoted context omitted.

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…

I found the fork / refactor of VIM by NeoVIM to be very hostile and even naming itself "New Vim" made me not want to support NeoVIM. I have been using VIM since it was on my Amiga in the mid 90s. VIM has been a stellar project that is due a lot of respect. Even the funding for VIM is reflected back to giving to Uganda children charity. > NeoVim exists at all is because Bram Moolenaar refused to accept any patches for…

It's offensive for neovim to call itself neovim but it's alright for vim to be called vim? For the record, vim means Vi iMproved. Bill Joy invented Vi, not braam.

Neovim is very much to vim what vim was to Vi.

And Vi is what should be credited for the more important concepts found in those editors and their reproduction in IDE like the various Vi like plugins.

Braam losing a spiritual monopoly on such a great editor concept like Vi can only be a good thing.

For something you call worse than unity, it works pretty nicely, stable, fast, with far more readable code and is already on its way to become a great embeddable editor so that we can use the real Vi in IDE instead of pale imitations.

Post reply on HN