Neovim v0.6.0 Released

[ziihrs]

https://github.com/neovim/neovim/releases/tag/v0.6.0

[deckiedan]

Congratulations neovim team!

Is there a "top 5 features" of 0.6? Seems like a million bugfixes and lsp/tree sitter tweaks... But what new things will come from here?

[mjlbach → deckiedan]

Random neovim maintainer here:

These are just my top 5.

* vim.diagnostic (see gpanders talk at https://www.twitch.tv/videos/1220189913?t=00h58m27s)

* vim.json (api-fast safe json deserialization with vendored lua-cjson)

* virtual lines (https://github.com/neovim/neovim/pull/15351)

* lua bindings to xdiff (https://github.com/neovim/neovim/pull/14536)

* a million bugfixes as you say :)

I personally worked on fixing utf handling around the built-in language server client, rewriting the incremental sync algorithm, vim.json (the built-in language server client is now fine with typescript-language-server thanks to the deserialization improvements), amongst various other small improvements.

[ahurmazda → mjlbach]

Thank you for all y'all hardwork. Neovim has become my workhorse since 0.5 and I am loving it.

I am excited about the virtual lines. Quite a few possibilities there.

[sieste → ahurmazda]

I don't understand what the new virtual lines feature does. Can anyone explain?

[ahurmazda → sieste]

The way I picture it is having true N number of lines on your working buffer that does not interfere with the actual line count in your file. We already have virtual-texts in neovim that only can show up on the same line as existing texts.

Pay close attention to the line counts in the image (from original PR) https://user-images.githubusercontent.com/1363104/129208266-...

[epage → deckiedan]

In my skimming, it sounds like its mostly targeted at plugin developers. The main directly user-impacting part seems to be the adjustments to defaults.

[maxioatic]

Nice! I bet this feels good for the team after the almost year between 0.4 to 0.5. Hopefully they take some time off this winter!