From: "Carlo Marcelo Arenas Belón" <carenas@gmail.com>
To: git@vger.kernel.org
Cc: sandals@crustytoothpaste.net,
"Carlo Marcelo Arenas Belón" <carenas@gmail.com>
Subject: [RFC PATCH] editorconfig: limit code lines to 80 characters
Date: Mon, 22 Jan 2024 12:14:20 -0800 [thread overview]
Message-ID: <20240122201420.72802-1-carenas@gmail.com> (raw)
Since 6f9beef335 (editorconfig: provide editor settings for Git developers,
2018-10-08) a multi editor/IDE configuration file has been provided to help
developers follow Documentation/CodingGuidelines.
The settings are also supposed to mirror what is found in .clang-format, but
the "ColumnLimit: 80" setting wasn't included, so correct that.
---
.editorconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/.editorconfig b/.editorconfig
index f9d819623d..c6d7815c80 100644
--- a/.editorconfig
+++ b/.editorconfig
@@ -7,6 +7,7 @@ insert_final_newline = true
[*.{c,h,sh,perl,pl,pm,txt}]
indent_style = tab
tab_width = 8
+max_line_length = 80
[*.py]
indent_style = space
--
2.39.3 (Apple Git-145)
next reply other threads:[~2024-01-22 20:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 20:14 Carlo Marcelo Arenas Belón [this message]
2024-01-22 20:44 ` [RFC PATCH] editorconfig: limit code lines to 80 characters Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240122201420.72802-1-carenas@gmail.com \
--to=carenas@gmail.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).