-
Notifications
You must be signed in to change notification settings - Fork 319
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add basic EditorConfig file #256
base: trunk
Are you sure you want to change the base?
Conversation
https://editorconfig.org/ From the site: "EditorConfig helps maintain consistent coding styles for multiple developers working on the same project across various editors and IDEs. The EditorConfig project consists of a file format for defining coding styles and a collection of text editor plugins that enable editors to read the file format and adhere to defined styles. EditorConfig files are easily readable and they work nicely with version control systems." Most editors / IDEs are supported
There is a good list of projects using EditorConfig: https://github.com/editorconfig/editorconfig/wiki/Projects-Using-EditorConfig |
I suggest we add: A page on our wiki suggests to use 4 spaces for indentation, so we could also add:
to the same section. |
Wiki is often outdated. Would that correspond to: /* vim: set noet sw=4 ts=4: */ |
...but I liked it that way... ;-) In fact, I thought that that wiki page was written after many files were already formatted with tabs. It may be worth a short discussion on dev@.
This should represent the current state of many files, i.e. tabs, to be displayed as 4 spaces. I was suggesting we rather set |
I looked further and now I agree that this is our current standard. Yes, the wiki is outdated. So this PR shall only add:
|
https://editorconfig.org/
From the site:
"EditorConfig helps maintain consistent coding styles for multiple developers working on the same project across various editors and IDEs.
The EditorConfig project consists of a file format for defining coding styles and a collection of text editor plugins that enable editors to read the file format and adhere to defined styles.
EditorConfig files are easily readable and they work nicely with version control systems."
Most editors / IDEs are supported