nvim-config-local VS editorconfig-vim

it's been undeprecated recently, but if you would prefer to use a plugin, I use this one

The next version of neovim (and currently, nightly) re-enables support for exec, which sounds close to what you want. In the meantime check out https://github.com/klen/nvim-config-local. These both do a single file, but once you're running some code it's easy enough to get that file to source more.

I just use nvim-config-local, which is basically just souped up :h 'exrc'. And then from there I typically set makeprg and a custom "run" command if I want, along with any other settings I might want in the project. I tried using some custom runner type plugins in the past but I think this method has provided me with the most flexibility, and I don't have to learn anything new because it's just the same as what i do in my init.lua.

I took inspiration from nvim-config-local and added an integrity check, to force the user to review the settings file at least once. It's on by default, but is optional. The file can be safe to use if you don't expose any option that allows for arbitrary code execution.

nvim-config-local

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.