Skip to content

Conversation

@ibbem
Copy link
Collaborator

@ibbem ibbem commented Jun 12, 2025

This prevents annoying issues with inconsistent formatting (most notably it should enforce consistent whitespace usage in new files) and misconfigured editors (e.g., editors which always try to fix the formatting of the whole file, without explicit request). This also starts tackling #136 whose motivation was exactly the same, although mostly limited to Java files.

Copy link
Member

@pmbittner pmbittner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks great to me! Thanks for the helpful comments in the commit messages, in particular regarding git blame.

@pmbittner
Copy link
Member

pmbittner commented Jun 13, 2025

I leave it to you when to merge this PR when you like, in case it causes annoying merge conflicts with other parallel changes.

ibbem added 2 commits June 13, 2025 16:10
I checked all hand written text file extensions in use and most of them
already use 4 space indent majorly. The only exceptions are *.sh, which
is a wild chaos were any arbitrary decision will do, and *.nix where two
space indenting is prevalent in the Nix community (i.e., Nixpkgs).

See https://editorconfig.org/ for the specification and the goals of
`.editorconfig` files.
If you try to blame, log or similar and hit this commit, use `-w` to
skip commits like this. For example `git blame -w`.
@ibbem ibbem merged commit b90154e into develop Jun 13, 2025
2 checks passed
@ibbem ibbem deleted the editorconfig branch June 13, 2025 14:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants