Neovim 0.3 released (opens in new tab)

Clipboard seems to work well for me with this config:

    set clipboard+=unnamedplus

More details on that here: https://neovim.io/doc/user/provider.html#provider-clipboard

A couple of small things I really like:

    :set inccommand=nosplit

... this gives you a live view of substitutions as you type out a replacement e.g :%s/foo/bar/

    :term
    :vs term://bash

... these gives you a proper embedded terminal window inside vim.

Also, I think vim8 has it as well, but something people might not realise is you can use truecolor gui color schemes (not limited to 256 color) in the terminal with

    :set termguicolors

It also has a guicursor option for making the cursor display as a block or bar in the terminal depending on which mode you're in: https://neovim.io/doc/user/options.html#'guicursor'

Other than that, there's a more thorough list of differences here: https://neovim.io/doc/user/vim_diff.html

My pet favorite: opening a terminal in a vim split.

Having an interactive bash/ipython/repl session where you can use vim keys to navigate and yank lines from your scrollback is pure bliss.

I like to run builds and be able to see, yank, open files from the errors all inside vim.

For me neovim brought true color themes support in the terminal, which was a breath of fresh air, or rather a major relief for my eyes. I switched to it for that reason, and using it ever since.

The main benefit of Neovim for me is support for async jobs.

So, for example, if you have autosave enabled, it won’t block the UI while it’s writing to disk.

A working workaround for me was to alias vi to `gvim -v` instead. It launches gvim without the GUI (so... vim), but still keep clipboard support.

Taking a stab, but you're not using Vim under tmux on a Mac, are you? If so, you need to do a tweak to get clipboard access.

https://robots.thoughtbot.com/how-to-copy-and-paste-with-tmu...

Otherwise the "+y / "+p commands should yank and paste system clipboard correctly.

The differences are very small. I use both, nvim for programming, and vim for everything else. This is for no real reason - it's just turned out that way. Some programming-related plugins I use work better on neovim, although there are also some where it's smoother sailing on vanilla.

I rarely notice any difference whatsoever in terms of behaviour.

You don't need to compile vim for clipboard support these days. On Mac, `brew install vim`, on Ubuntu `apt-get install vim-gtk`. The latter I think comes with the gui version of vim but you don't have to use it, it also includes a `vim` binary with clipboard support.

Can't answer about copy/paste an NeoVim, but I just switched from vim -> neovim this week, and do feel it's a bit snappier. I also switched from syntastic to ALE for syntax checking and that made a huge difference as well.

For copy/paste in the terminal and vim, I usually have vim in a tmux session, and that has a few helpers to work with system clipboards. Not perfect, but better than vanilla vim's copy/paste.

Re: your clipboard issues, which platform are you running on? I am using vim+iTerm2 on OSX and vim+st on OpenBSD and the clipboard integration works flawlessly.

it's slightly faster to start up, is a big one

For the record, I don't think nvim is much better, but there's definitely stuff that doesn't work out of the box in Vim. For instance, the Alt key was a real struggle for me. Clipboard support is the same for a lot of people. Both of these things are for reasons, but still.

I've just switched to Oni, and would highly recommend it for someone who wants a Vim with the best features of modern graphical editors like Visual Studio Code. Oni does have some rough edges, since it's still pre-1.0, but it is largely feature-complete, with Language Server Protocol support, lightning-fast search powered by ripgrep, a command palette etc.

According to the README of that project, it does not support snippets nor auto-complete yet. Seems to be very alphaish..

Not really a frontend on Vim or NeoVim though are they? They’re emulations which are very nice but not the real thing.

It’s the uncanny valley situation again. For example, in Vim, like all terminals by default you can use C-h as backspace. In Emacs though that’s bound to help.

So now I have to rebind that and make a decision on what should now be help. That’s just the start on the thread pulling and tweaky just to get back to my expected behaviour.

Emacs is great but it’s not Vim. You could argue thatonce configured you have all the new power of Emacs but ome of just want a better Vim. Not Emacs. Even if it’s brilliant.

I can specifically recommend doom-emacs.

I'm the author. ActualVim feels pretty slick out of the box. The main issue is in parts of the Vim UI that aren't integrated yet (I'm praying for more UI customization options from Sublime Text, though the recent command palette improvements should be a great start for replacing the command line).

The actual editing should be really solid, even if you use Sublime Text features to manipulate text. It's typically very fast too, I try to beat 16ms handle time per keystroke on all platforms (so updates land within a frame).