37
What's New in Neovim 0.11 | g.p. anders
gpanders.comNeovim 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.
So LSP is finally usable without setting up and installing a dozen things for each language?
It turned out to not change much in practice for end users I think. We still want the lspconfig plugin for default settings for the most common LSPs, but setting up without it should be more straightforward. The lspconfig plugin will also be transitioning to the new configuration method.
I tried with Lua. I installed the language server and followed the instructions and fiddled with it until it worked, doing multiple web researches over a time of 40-60 Minutes.
All I got was a bunch of
Wfor lines where I used global variables, and some underlined text with “no information available” and a table variable showing what keys the table has.No autocomplete, no information on parameters, no nothing.
This is not good or convenient at all and we should stop lying to ourselves. LSP in Neovim is utterly annoying and complicated to set up properly.
IDK, I’ve mainly used the lspconfig plugin and haven’t really had problems in general, but some LSPs seem weaker than others
you need a completion plugin. I am using blink.cmp its great also lsp-signature plugin for signature help