pantran.nvim VS plenary.nvim

What is the difference to pantran.nvim?

This one is better! https://github.com/potamides/pantran.nvim

Story time: I really love Neovim for programming, but one thing I love it even more for is scientific writing. Tools like texlab make this especially fun! But for a well-rounded experience, I need a few more things: (i) Grammar checking. For that I can recommend ltex, an LSP-server which adds LaTeX support to language tool. (ii) Thesaurus lookup. (Neo)vims integrated thesaurus format is a little bit limited. But thankfully 'thesaurusfunc' exists so I could easily write a small plugin to add support for openoffice.org mythes thesauri. (iii) Machine translation. Now we're finally getting to the topic of this post. I write most of my stuff in English but I'm not a native speaker, so machine translation is valuable for me. It can help me to overcome writers block to an extent, for example. There already exist a few plugins for that problem, like vim-translator or translate.nvim. But none of these support interactive modes, a slick UI, and, as far as I know, useful things like motions and counts. This is where my plugin pantran.nvim comes into place! The demo should speak for itself. In the end it was a lot more effort than I anticipated but I'm very pleased with the result. I hope this can be useful to others as well!

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