Live data from Hacker News

NeoVim 0.2.0 released

github.com

121–130 of 141 posts

Re: NeoVim 0.2.0 released

#121
post #113

Earlier quoted context omitted.

Your wrong in terms of how VIM came about and name. VIM originally meant "Vi IMitation". It wasn't till 1993 that it became "Vi Improved." Actually VIM is not a direct fork of VI. VIM comes from Stevie editor from Atari ST and Amiga days. (I actually started with Stevie). Here is the tree from ed to VIM ed > Bill Joy and company then made em > en > ex AKA vi Joy left development of VI in June 1979 and joined corporat…

I think the reason people are downvoting you is that after the (interesting) historical detour, you say "it is not at all like this fork" when in fact it is still exactly like this fork as far as the main point of the parent post is concerned. Due to _________ we are making a clone of this other product, but one that fixes ________, and therefore we are also attempting to co-opt the name a cutesy way so that people u…

> Due to ________ we are making a clone of this other product,

LICENSING (owned by AT&T the Oracle/Apple Grand Daddy of lawsuits in the 80s and 90s) and it was a port on an unsupported operating system, Amiga OS.

Also it was a clone of Stevie more so then Vi.

> but one that fixes ________

Vi TO RUN ON AMIGA OS (ADDED PLUGINS and CUSTOMIZED SHORTCUTS plus many other features not found in VI.)

Nothing in Neovim especially looking at VIM 8.0 is added but it is a refactoring with compatibility of plug ins with a cleaner code base.

I feel like people on NeoVIM side never really read the primary fights about the patch or understood why BDLF took a stand for a code more to his liking.

Re: NeoVim 0.2.0 released

#122

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…

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.

Try Vimr (on GitHub). It is amazing.

Re: NeoVim 0.2.0 released

#123
post #5

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

I think the current goal is to let neovim instances to communicate p2p so that they transparently use the same session. Mostly because adding multi-tenancy to vim would be a living hell without adding much over that approach.

Has been a while since I have read up on that, though.

Re: NeoVim 0.2.0 released

#124
post #47

Earlier quoted context omitted.

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

I saw this thread, and I promised myself I wasn't going to plug Kakoune -- I think NeoVim is a great project and I want it to succeed. They deserve every bit of the praise they're getting. But I'm going to have to break my promise, because Kakoune has the exact feature you're after, and I'm using it right now. That, along with familiar keybindings, selection-oriented modal interface, tmux integration... I could go on…

Kakoune is always super tempting to me but the plugin thing is a deal breaker for me. Not for IDE-like features but because limiting myself to vanilla vim motions feels like using a bad vim plugin by now.

At least surround.vim, targets.vim and a couple custom text objects.

Re: NeoVim 0.2.0 released

#125
post #85
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 set up a new machine a couple of days ago. Looked for neovim in FreeBSD ports. It wasn't there. Shrugged and installed vim. I'd happily have switched if only for the code quality reputation. But it needs to be easy - no, that's too weak a word, it needs to be trivial - to install in the usual way I install things.

This is incorrect, neovim is available in the FreeBSD ports. [1]

[https://svnweb.freebsd.org/ports/head/editors/neovim/]

Re: NeoVim 0.2.0 released

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

AFAIK, the main feature neovim will have is the ability to replace viml with lua wherever you want to.

According to the roadmap[1], lua will be built-in in 0.3.

[1] https://neovim.io/roadmap/

Re: NeoVim 0.2.0 released

#127
post #32
post #28

Earlier quoted context omitted.

I'm an Emacs user and that's because the Unix way doesn't quite work out well in practice: composition is hard, requires textual transformation with many possible edge cases as glue which is hard to build and maintain and is bug-prone, and interfaces are cryptic, only partly portable and inconsistent. Elisp on the other hand is a nicer primitive for building my day-to-day tools: Uniform data format everywhere; buffer…

I used vim and neovim for quite some time and eventually switched back to Emacs. The "you do not have to leave your environment" is actually quite nice. magit and org-mode are awesome. Color scheming is actually easier. Still having trouble with identation, though. vim is just smarter ...

> Still having trouble with identation, though. vim is just smarter ...

While that is still generally true in my experience, it helps a lot to set c-style indentation to linux-style instead of gnu-style.

From the top of my .emacs:

    (setq c-default-style "linux"
          c-basic-offset)

Re: NeoVim 0.2.0 released

#130
post #43

Earlier quoted context omitted.

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?

I use a plugin ranger.vim [1]. Although it works for plain VIM, it is very clunky, since ranger is opened with a !command you get a blocking terminal.

The nesting really is tmux -> Shell -> Nvim -> Ranger.

https://github.com/francoiscabrol/ranger.vim

Post reply on HN