I have no idea but am fine for it.

Can you describe this PR's motivation? I think format rules for C, C++, Fortran, and Python are already in .pre-commit-config.yaml and applied in every commit

Different users may have different settings for indentation and line length; a formatter enforces the style, but it may bring big diffs, which will be reduced by editorcondfig as far as user’s editor supports it.

And I found that currently clang-format and ruff do not modify EOL, CR vs CRLF, which is configurable by:

• .editorconfig
• .gitattributes
• .clang-format
• ruff.toml

I like the idea of this project, but it does overlap with pre-commit, specifically the EOL and CRLF is enforced by

We are missing mixed-line-ending though, could you open one enforcing LF line-ending?

I would suggest punting this in favor of specialized tools that do overall formatting until it can be used for general language settings ¹.

Ideas for Domain-Specific Properties

The following properties are not intended to be implemented by EditorConfig.
This is simply a brainstorm of domain-specific properties that could be supported by some tools that rely on EditorConfig files.

There is a proposal to "namespace" properties with a language-dependent prefix. See Issue #332.

For now the IDEs should have support for ruff and clang-format which are our main formatters. I did notice that we are missing badges for our styles, would be nice if we can get a PR to advertise badges for pre-commit, ruff, clang-format that we use.

I am using neovim, which now natively supports EditorConfig but does not load configs from .clang-format etc unfortunately. (maybe there exists some plugins)
I believe EditorConfig is simple and universal, and complicated styles can be achieved by the specific formatters.

That’s why I opened this PR for less surprising.

@LecrisUT and @lan496 , can this PR be merged?

Can I merge @e-kwsm and @LecrisUT?

Can I merge @e-kwsm and @LecrisUT?

The pre-commit is failing because the database file is not skipped. We need to add a setting in .editorconfig to skip those for now. Once the pre-commit passes, yes we can merge

@e-kwsm I have made some changes to minimize the diffs, can you check if everything looks fine to you as well.

Is it ready to merge?