nvim-starter VS plenary.nvim

Minimal init.lua.

This one is more of an example config.

nvim-starter - modular

I'm working on a config inspired by features people like about helix. Here's the link: nvim-starter - light

Minimal example config

And to be a bit more specific, the branch 05-modular in nvim-starter is the one that uses all the lazy-loading goodness in lazy.nvim.

Also this one: https://github.com/VonHeikemen/nvim-starter

There is a branch with a minimal setup. I mainly use it for testing but it is a good example.

I have this repo nvim-starter, in there you'll find resources of all kind. There is an example configuration split in several branches, you can see the evolution from a simple config with no plugins to a modular opinionated config (using lazy.nvim). In the config branches you'll also find links to blogposts that explain the code in the repo. Hope that helps.

Here's an example config using it: nvim-starter - lsp-cmp

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