From: Thomas Schwinge <thomas@codesourcery.com>
To: Marc Poulhies <poulhies@adacore.com>
Cc: <gcc@gcc.gnu.org>, Alexander Monakov <amonakov@ispras.ru>,
Iannetta Paul <paul.iannetta@ens-lyon.fr>,
David Malcolm <dmalcolm@redhat.com>, <gcc-rust@gcc.gnu.org>
Subject: Re: Setting up editors for the GNU/GCC coding style?
Date: Fri, 29 Jul 2022 11:29:03 +0200 [thread overview]
Message-ID: <874jz09sio.fsf@euler.schwinge.homeip.net> (raw)
In-Reply-To: <8735ekmkty.fsf@adacore.com>
Hi!
On 2022-07-29T09:36:41+0200, Marc Poulhies via Gcc <gcc@gcc.gnu.org> wrote:
> Iannetta Paul <paul.iannetta@ens-lyon.fr> writes:
>> About configuring recent editors to follow the GNU coding style, I don't really
>> know but it should always be possible to register a hook that will run `indent`
>> when the file is saved.
>
> There is a clang-format config file in contrib that one can symlink in
> the root dir as .clang-format. I hope/guess tools like CLion can pick it
> and use it? At least this can be used to indent using clang-format tools
> and derivatives (like git-clang-format). In the GCC Rust project, we are
> using it (but judging by Jakub's last review for Philip's patch, the
> config is maybe not exhaustive, or our setup is not correct).
Simple answer there: these files are in 'gcc/config/' etc.,
but 'clang-format' is restricted to 'gcc/rust/' only (both in
'.github/workflows/clang-format.yml' and 'CONTRIBUTING.md':
"Running `clang-format` locally").
Unless everyone uses it, using 'clang-format' everywhere is too noisy;
it has a very strict (in my opinion: restrictive) understanding of
"proper" format. ;-)
Grüße
Thomas
-----------------
Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
parent reply other threads:[~2022-07-29 9:29 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <8735ekmkty.fsf@adacore.com>]
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=874jz09sio.fsf@euler.schwinge.homeip.net \
--to=thomas@codesourcery.com \
--cc=amonakov@ispras.ru \
--cc=dmalcolm@redhat.com \
--cc=gcc-rust@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=paul.iannetta@ens-lyon.fr \
--cc=poulhies@adacore.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).