commit cc09ff253e2516ea3bc4bdd7fa8c6052b36900e6 Author: juga0 juga@riseup.net Date: Mon Jun 11 21:29:40 2018 +0000
Add explanation about editorconf in coding standards
so that developers know what is .editorconfig for. --- doc/HACKING/CodingStandards.md | 3 +++ 1 file changed, 3 insertions(+)
diff --git a/doc/HACKING/CodingStandards.md b/doc/HACKING/CodingStandards.md index 3711f7019..4a8f13716 100644 --- a/doc/HACKING/CodingStandards.md +++ b/doc/HACKING/CodingStandards.md @@ -185,6 +185,9 @@ deviations from our C whitespace style. Generally, we use: `puts (x)`. - Function declarations at the start of the line.
+If you use an editor that has plugins for editorconfig.org, the file +`.editorconfig` will help you to conform this coding style. + We try hard to build without warnings everywhere. In particular, if you're using gcc, you should invoke the configure script with the option `--enable-fatal-warnings`. This will tell the compiler