From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: <yann.morin@orange.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] .editorconfig: add editor-agnostic configuration
Date: Wed, 1 Nov 2023 22:54:23 +0100 [thread overview]
Message-ID: <20231101225423.2412f034@windsurf> (raw)
In-Reply-To: <5f5d6e6dbfc89ca509f3d73154d7e31d1b6659b5.1698759638.git.yann.morin@orange.com>
On Tue, 31 Oct 2023 14:40:38 +0100
<yann.morin@orange.com> wrote:
> From: "Yann E. MORIN" <yann.morin@orange.com>
>
> EditorConfig [0] is an editor-agnostic configuration file, to set
> preferences on how to edit text: tabs vs. spaces, tab width, indentation
> size, line endings...
>
> A large number of editors support EditorConfig, either natively [1] or
> with the help of plugins [2].
>
> Add a basic .editorconfig that provides defaults for most of the files
> used by Buildroot. More can be added in the future if we can find more
> matching patterns.
>
> The values are chosen a bit arbitrarily, unless we already have a
> (un)written rule about it. Notably, indentation defaults to using 4
> spaces, and only a set of files for which we require TABs (Makefile,
> essentially) or have already settled for TABs (Kconfig files, init
> scripts...) are configured so. The traditional width of TABs is 8 char,
> and we pair TAB indentation with TAB size.
>
> Trailing spaces are usually useless, except in asciidoc source where
> they can be used to force a new line without a new paragraph.
>
> One of the limitations of .editorconfig, tough, is that it matches on
> filenames (e.g. *.py), not on the content (e.g. no use of mimetype, or
> libmagic, or such). Still, this is enough to cover a lot of files in
> Buildroot.
>
> [0] https://editorconfig.org/
> [1] https://editorconfig.org/#pre-installed
> [2] https://editorconfig.org/#download
>
> Signed-off-by: Yann E. MORIN <yann.morin@orange.com>
> ---
> .editorconfig | 29 +++++++++++++++++++++++++++++
> DEVELOPERS | 1 +
> 2 files changed, 30 insertions(+)
> create mode 100644 .editorconfig
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-11-01 21:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 13:40 [Buildroot] [PATCH] .editorconfig: add editor-agnostic configuration yann.morin
2023-11-01 21:54 ` Thomas Petazzoni via buildroot [this message]
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=20231101225423.2412f034@windsurf \
--to=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin@orange.com \
/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