nvim-lsputils VS neovim-ui

some plugins you might wanna look into: https://github.com/RishabhRD/nvim-lsputils https://github.com/weilbith/nvim-code-action-menu

Have you tried nvim-lsputils? It's got some extra utilities that does provide better code actions from the LSP server, although I've only tried this in a JS/TS project and have the ability to auto-import via code actions.

RishabhRD/nvim-lsputils

decided i would drop this little plugin i wrote yesterday. much of the code is adapted from https://github.com/RishabhRD/nvim-lsputils, but using https://github.com/liuchengxu/vim-clap as the popup/preview and fuzzy finding ui.

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.