From: Jonathan Corbet <corbet@lwn.net>
To: Danny Lin <danny@kdrag0n.dev>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Andy Whitcroft <apw@canonical.com>, Joe Perches <joe@perches.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] editorconfig: Add automatic editor configuration file
Date: Fri, 3 Jul 2020 06:29:50 -0600 [thread overview]
Message-ID: <20200703062950.5e8c1785@lwn.net> (raw)
In-Reply-To: <20200703073143.423557-1-danny@kdrag0n.dev>
On Fri, 3 Jul 2020 00:31:43 -0700
Danny Lin <danny@kdrag0n.dev> wrote:
> EditorConfig is a standard for defining basic editor configuration in
> projects. There is support available for 47 code editors as of writing,
> including both built-in and extension support. Many notable projects
> have adopted the standard already, including zsh, htop, and qemu.
>
> While this isn't a full-fledged C code style specifier, it does set some
> basic ground rules that make it more convenient for contributors to use
> any editor of their choice and not have to worry about indentation, line
> endings, encoding, final newlines, etc. This should make it
> significantly easier to conform to the kernel's general code style when
> used in combination with clang-format.
>
> For more information, check the official EditorConfig website:
> https://editorconfig.org/
>
> Signed-off-by: Danny Lin <danny@kdrag0n.dev>
> ---
So I worry a bit that not everybody will welcome the addition of a dotfile
that may be magically interpreted by their editor. I also worry that the
file itself could become a battleground for people wanting to argue about
style issues.
Perhaps I worry a bit too much...?
jon
next prev parent reply other threads:[~2020-07-03 12:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-03 0:12 [PATCH] editorconfig: Add automatic editor configuration file Danny Lin
2020-07-03 5:38 ` Miguel Ojeda
2020-07-03 7:31 ` Danny Lin
2020-07-03 7:31 ` [PATCH v2] " Danny Lin
2020-07-03 12:29 ` Jonathan Corbet [this message]
2021-03-24 10:59 ` Rasmus Villemoes
2021-03-25 7:00 ` Masahiro Yamada
2021-03-25 9:44 ` Miguel Ojeda
2020-07-03 12:49 ` Matthew Wilcox
2020-07-03 17:22 ` Joe Perches
2020-07-03 7:49 ` [PATCH] " Miguel Ojeda
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=20200703062950.5e8c1785@lwn.net \
--to=corbet@lwn.net \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=danny@kdrag0n.dev \
--cc=joe@perches.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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