vim-addon-local-vimrc VS editorconfig-vim

You can? I'd never heard of this. Until now, I'd always used MarcWeber/vim-addon-local-vimrc. It works okay but if there's something built-in I'd much prefer that.

https://github.com/MarcWeber/vim-addon-local-vimrc does the job just fine.

Project-specific editor config: vim-localvimrc, vim-addon-local-vimrc

vim-addon-local-vimrc (project-local settings in a secure way, never use project-local settings without)

VERY IMPORTANT: Do not set your Neovim to automatically load such a file. Vim script files contain executable code and you do not want to load executable code unconditionally, that's a massive vulnerability. And no, setting the secure option does not help. I use this plugin which makes me first confirm that I want to load the file. From then on it will only automatically load the file if it has not been changed. If the file has changed it will prompt me again.

Try vim-addon-local-vimrc to load a project specific vimrc or vim-ctrlspace to load session infos.

I like monotasking - no plugins eating up screen real estate - so I use [vim-projectionist](https://github.com/tpope/vim-projectionist) and [vim-addon-local-vimrc](https://github.com/MarcWeber/vim-addon-local-vimrc). Projectionist allows me to capture the structure of my project: 'view', 'controller', 'test', 'component', 'feature-x-component', whatever. vim-addon-local-vimrc lets me configure projectionist (and other vim plugins) for my particular project.

Plugin: vim addon local vimrc

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.