editorconfig-vim VS vim-sleuth

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.

In addition to setting tabstop and shiftwidth, you might also like this plugin: https://github.com/tpope/vim-sleuth

vim-sleuth auto detects tab size so...

Just add https://github.com/tpope/vim-sleuth and never worry about it again.

At the end of the day I don't really care which a project goes with, I've always just used vim-sleuth to automatically set my tab key to input whatever the current file's indentation is.

VsCode has an internal function from auto-detecting indentation, while my config uses vim-sleuth with indent-blankline.nvim.

If you work a lot on legacy codebases, https://github.com/tpope/vim-sleuth is probably more what you need than editorconfig, as it will work even when one is not present.

The primary advantage of using it is that it has built in heuristics for detecting line wrapping when opening a file (with some Treesitter magic for Markdown to make it more accurate), and also allows for manual swapping between wrapping types. You can think of it as the wrapping equivalent to vim-sleuth.

I just found about Tim Pope's sleuth: https://github.com/tpope/vim-sleuth It supports editorconfig but it also seems to have just better heuristics when an editorconfig file isn't present, so I just decided to replace `editorconfig-vim` with it.

Another solution is try sleuth.vim, that sets automatically your indentation based on the project, buffer and editorconfig