GeistHaus
log in · sign up

Release Nvim release build · neovim/neovim

github.com

NVIM v0.12.2 Build type: Release LuaJIT 2.1.1774638290 Release notes Changelog (fixes + features) News (:help news in Nvim) Install Windows Zip Download nvim-win64.zip (or nvim-win-arm64.zip fo...

2 pages link to this URL
What's New in Neovim 0.11

Neovim 0.11 was just released. As in previous installments in this series, let’s talk a bit about some of the big highlights! As always, the full list of changes can be found in the release notes (use :h news to read inside of Neovim). Table of Contents Breaking Changes LSP Simpler LSP setup and configuration Builtin auto-completion Improved hover documentation Putting it all together Diagnostics Virtual text handler changed from opt-out to opt-in Virtual lines Defaults More default mappings Terminal Miscellaneous Breaking Changes We make a concerted effort to avoid breaking changes. We want the upgrade path between versions to be smooth and simple, but occasionally breaking changes are necessary (often times, a breaking change is a bug fix, or there is no way to introduce a transition path between old and new behavior). The full list of breaking changes can be found in the release notes (:h news-breaking). Plugin authors are especially encouraged to carefully read this section, as many of the changes have to do with “lower level” APIs.

4 inbound links en CC BY-SA 4.0
What's New in Neovim 0.11

Neovim 0.11 was just released. As in previous installments in this series, let’s talk a bit about some of the big highlights! As always, the full list of changes can be found in the release notes (use :h news to read inside of Neovim). Table of Contents Breaking Changes LSP Simpler LSP setup and configuration Builtin auto-completion Improved hover documentation Putting it all together Diagnostics Virtual text handler changed from opt-out to opt-in Virtual lines Defaults More default mappings Terminal Miscellaneous Breaking Changes We make a concerted effort to avoid breaking changes. We want the upgrade path between versions to be smooth and simple, but occasionally breaking changes are necessary (often times, a breaking change is a bug fix, or there is no way to introduce a transition path between old and new behavior). The full list of breaking changes can be found in the release notes (:h news-breaking). Plugin authors are especially encouraged to carefully read this section, as many of the changes have to do with “lower level” APIs.

0 inbound links en CC BY-SA 4.0