summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaniel Kahn Gillmor <dkg@fifthhorseman.net>2022-01-08 11:31:59 -0500
committerDaniel Kahn Gillmor <dkg@fifthhorseman.net>2022-01-08 12:05:53 -0500
commit463483fbc9e4ad1a373a22f27532d98234488cae (patch)
tree4d8a7588206a3fe01e891db45d76421dc93f8ea4
parent54da436258d79b683f57dfadf787bdf56ca58576 (diff)
downloadlibgnomekbd-463483fbc9e4ad1a373a22f27532d98234488cae.tar.gz
Add .editorconfig for easier communication of code conventions.
Many editors support .editorconfig. From looking at some of the code in libgnomekbd (i've really only been playing around with the C code), it appears to be using the configuration directives I've documented here. The conventions documented here aren't my personally preferred conventions, but I find it it useful to let my editor know what the project uses, so that i can contribute without thinking too much about whitespace, etc. If there are other conventions, this gives people a place to add them. Or, if the project wants to update the conventions, it provides a place to document those changes.
-rw-r--r--.editorconfig15
1 files changed, 15 insertions, 0 deletions
diff --git a/.editorconfig b/.editorconfig
new file mode 100644
index 0000000..98e0578
--- /dev/null
+++ b/.editorconfig
@@ -0,0 +1,15 @@
+# see https://EditorConfig.org
+
+# top-most EditorConfig file
+root = true
+
+# Unix-style newlines with a newline ending every file
+[*]
+end_of_line = lf
+insert_final_newline = true
+
+# Matches multiple files with brace expansion notation
+# Set default charset
+[*.{c,h}]
+indent_style = tab
+indent_size = 8