nui.nvim VS plenary.nvim

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

we can create a function to open a pop up menu using plenary.popup like this, you need to install neovim plenary if you don't already have it https://github.com/nvim-lua/plenary.nvim

If you are really interested in doing this yourself with loop, you should take a look at either plenary.job or netman.shell (I made the latter) as both are very well documented.

I feel this :( That said, alot of plugins rely on plenary.nvim. Its up to you if you determine this is "non-essential" or not. It will almost certainly be available for you to use already.

The big reason I ask is that reaching out to an external python shell to run commands (disregard the fact that its python running) is going to be much slower than using the in built lua JIT interpreter. Additionally, plenary has a built in curl function so you don't have to "reinvent the wheel".

There is also test harness in nvim-lua/plenary.nvim with a slightly different design, but still usable of course.

I am simply using busted or more specifically vusted which is a wrapper around busted for Neovim. It should be quite straightforward to learn the basics, I would say you mostly need to know these functions: describe, it (these are used to structure your test cases) and assert.are_same (to check for table equality). Some people are also using plenary which is also based on busted.

It's based on nvim-lua-plugin-template, but uses Nix flakes to run plenary.nvim tests.

Plenary plugin for Nvim