neovim-ui VS LunarVim

mjlbach/neovim-ui

I understand the frustration (making neovim more cohesive is definitely a goal). It sounds like coc provides the UI you are used to, so there's no harm in sticking with that!

Many of our users explicitly don't want automatically called functions that would slow down the editor (autocommands that map signature requests to the language server, for example), so by nature neovim's core implementation is extremely conservative.

One thing I would like to do, is make the automatic pop-ups for signature easier to implement with our current handler, which means a plugin like signature-x could use our upcoming lsp.config option to configure it's borders (https://github.com/neovim/neovim/pull/14681), and match the rest of the UI.

I also have another project I was working on before the 0.5 stabilization phase (https://github.com/mjlbach/neovim-ui). The goal with this is to have composable/overridable UI elements built into core (which we would use for our internal lsp functions), that can be used (or overridden) by UI plugins.

In summary, I think the likelihood of autocompletion (and generally auto-anything) being built-into core is very small, but providing the APIs in neovim core to make snippets - autocompletion - automated UI elements easier for plugin authors is a high priority.

Yep, I started working on this awhile ago https://github.com/mjlbach/neovim-ui but put it on hold for 0.5 stabilization.

I am working on this, but it will probably have to wait until after the 0.5 release (I don't know when this will be). This is part of the larger UI effort in neovim-ui which is currently glorified vaporware. As far as I know, TJ, Smolck, and I are the only ones who have expressed interest in fixing this.

LunarVim

I would suggest to start getting into vim by first trying out popular vim keybinding plugins available on your favorite code editor and get used to those first. Then, if you want to dive deeper into the power of Neovim, try out popular configs like LazyVim, LunarVim, NvChad... Taking Neovim from a mere text editor to a full-featured IDE with features like intellisense, debugging, testing, etc... on your own takes quite a lot of work and configuration.

I used Helix for a while due to its support for LSP out-of-the-box, which my Vim config at the time couldn't live up to. I switched back to NeoVim after finding LunarVim[1] which had everything I was trying to get setup in my own config.

[1] https://www.lunarvim.org/

I'll admit I didn't look into it, but Helix sounds like something like LunarVim (https://www.lunarvim.org/)

Personally I much prefer that the editor NOT ship with something like that by default, especially when it's so easy to set up. I have several different vim config I use, including a pretty bare-bones one for headless systems, and I much prefer the ability to customize something very specifically.

Build tools that can compose together, rather than a single do-it-all tool. That is the power of the low level editors vs IDE's.

I can't comment on any implementation details, but at least with LunarVim (which I use for daily coding), a slowdown when interacting with LSP is very noticeable. Some others have attested to this on a GitHub issue.

I'm not doubting your experiences with the lack of a slowdown, but there is truth that others do experience it. That might be more of a problem with LunarVim itself rather than Vim, but how likely am I (as someone who would like to avoid what he calls "config hell") or other newcomers to avoid whatever pitfalls there are, if a distribution designed for ease of use by people who know better fall into them?

https://github.com/LunarVim/LunarVim/discussions/3359

Anyways, although i have not used them, LazyVim and LunarVim comes highly recommended. You can try these and see what suits you .