plenary.nvim VS editorconfig-vim

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

These are tools that you need to add. But the most elemental code formatting is not here, it is in the widely supported .editorconfig file.

Hello,

Maybe you should check this project:

https://editorconfig.org/

Regards,

editorconfigchecker. A linter that checks files for compliance with editorconfig rules. Another linter that helps maintain consistency in the format of all files.

Oh, yeah, we had that issue too and solved it pretty successfully with `.editorconfig` (shareable between VScode and IntelliJ, https://editorconfig.org/) combined with `prettier`.

Each IDE is configured to:

- Not reformat code on its own

- Ignore whitespace

- Run `prettier` as a pre-commit hook

Those settings are saved to `.editorconfig` where possible, or to each IDE's repo-specific folder (e.g. `.idea`).

Then in theory each developer can use whatever IDE they want, whatever whitespace settings they want (tabs vs spaces), and the end code committed to the repo is still the same.

I am aware of .editorconfig, and one day that may be the correct answer but the specification does not support every element of the styles of both oss and css.

Does this mean I can completely get rid of this plugin?: https://github.com/editorconfig/editorconfig-vim

[1] https://editorconfig.org

I dunno who downvoted your question, but I believe you can use .editorconfig to set that up for you.