nui.nvim VS neovim-ui

Perhaps nui.nvim could be the foundation for a more graphical nvim?

That was just a demo, replacing the content of the cell under cursor to "Poof!". The code for that demo is here: https://github.com/MunifTanjim/nui.nvim/pull/260

I get the same problem with it, but NUI's input doesn't exhibit this problem.

For keybindings specifically, folke/which-key.nvim. If you actually want to create your own, the most popular UI component plugin that I can think of is MunifTanjim/nui.nvim

There is a way to fix them, but it's quite tricky, would require quite some work, and also requires a terminal with support for the kitty graphical protocol: https://github.com/MunifTanjim/nui.nvim/pull/107

Not at this moment. But it's on the way: https://github.com/MunifTanjim/nui.nvim/pull/138

nui.nvim, provides nice "components" for inputs, selects, popups.

Have you checked NuiTree from https://github.com/MunifTanjim/nui.nvim ? You can either use it directly or see the source code to have an idea about the implementation.

LMGTFY... https://github.com/MunifTanjim/nui.nvim

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.