nvim-lua VS plenary.nvim

I recently converted vim-tmux-navigator to lua via a simple function and using A-hjkl\ binds (which has no conflicts) instead of the default C-hjkl\, feel free to reuse my code, relevant commit.

source: https://github.com/ibhagwan/nvim-lua/blob/main/lua/lsp/rename.lua

I guess this is a preference thing, I would consider my config my config highly customized and pretty advanced, it has almost 8k lines of code, I don't fiddle with it as much as when I just converted to lua but I still update ocasionally and I find lua perfect for the job, instead of macros I just create small lua functions in order to avoid code duplication (where applicable).

I'm not just giving you complements to boost your morale, I've seen your code first hand, I've used feline (we even interacted in issues) and also copied your archived nvim-reload code into my config and can recognize a good programmer when I see one.

Technically all you need to do is set package.loaded[module] = nil for all the modules you wish to reload and that's why my modded version does, it reloads all your entire neovim config and all the plugins listed in the linked init file.

FYI, just added this to my config with a slight twist (resize back once I'm done), this so great :)

My config isn’t a “permade”, it’s not meant to be a solution for anyone other than myself, nevertheless you might find it useful for plugin selection and some cool functions.

You can view my setup here.

My own version of Embark colorscheme and feline.nvim, my configuration can be found here

Btw, if anyone wants the “evil-line” equivalent config for feline you can find it here

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.