this-week-in-neovim.org VS editorconfig-vim

In terms of actual infrastructure changes, I’ll keep helping around if needed, but codico already did a lot of work to come up with their own new, refreshed and more pleasant to the eye TWiN. What I’m doing now is to set redirection to their hosts, so it’s not unlikely that https://this-week-in-neovim.org will remain down for a couple of hours / maybe days until the transition is done smoothly.

As long as I still have https://this-week-in-neovim.org I’m fine 😃

There's overseer.nvim to run all sorts of things and neotest to run tests. In general, you can check awesome-neovim or TWiN to look for plugins.

Either wait for Monday 9:00 AM (or 10:00, I don’t even recall; I’ll check that later), or if it’s past due (which can happen depending on my spare-time activities / work), **directly connect to the machine hosting this-week-in-neovim.org and git pull --rebase to get the updates.

"This Week in Neovim" occasionally features a "Did You Know?" section with a tip which is sometimes applicable to Vim, although there haven't been one in the past couple of months.

This Week in Neovim

This Week in Neovim for staying up to date with new plugins every Monday.

It stands for "This Week in Neovim" see also https://this-week-in-neovim.org/

.editorconfig helps maintain consistent coding styles for multiple developers working on the same project across various editors and IDEs. Find more information on the EditorConfig website if you’re curious.

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