[libgnomekbd: 1/2] Add .editorconfig for easier communication of code conventions.
- From: Corentin Noël <corentinnoel src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [libgnomekbd: 1/2] Add .editorconfig for easier communication of code conventions.
- Date: Tue, 14 Jun 2022 11:22:34 +0000 (UTC)
commit 463483fbc9e4ad1a373a22f27532d98234488cae
Author: Daniel Kahn Gillmor <dkg fifthhorseman net>
Date: Sat Jan 8 11:31:59 2022 -0500
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.
.editorconfig | 15 +++++++++++++++
1 file changed, 15 insertions(+)
---
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
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]