public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Richard Earnshaw <Richard.Earnshaw@foss.arm.com>
To: Iannetta Paul <paul.iannetta@ens-lyon.fr>,
	Alexander Monakov <amonakov@ispras.ru>
Cc: gcc@gcc.gnu.org, Gcc <gcc-bounces+paul.iannetta=ens-lyon.fr@gcc.gnu.org>
Subject: Re: Setting up editors for the GNU/GCC coding style?
Date: Fri, 29 Jul 2022 13:34:45 +0100	[thread overview]
Message-ID: <6388d619-97da-5acb-cac4-53e2119b4fed@foss.arm.com> (raw)
In-Reply-To: <c8e42ea425cf665d0d3fe27b22ee1b17@ens-lyon.fr>



On 28/07/2022 22:43, Iannetta Paul wrote:

> 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.

I don't think that's a good idea.  It will result in quite a lot of 
minor changes that will just make diffs confused.  We do have a style, 
but not everything is exactly as GNU indent would lay it out (plus GNU 
indent says quite clearly that it can't handle C++).

R.

  parent reply	other threads:[~2022-07-29 12:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28 18:46 David Malcolm
2022-07-28 19:00 ` Alexander Monakov
2022-07-28 21:43   ` Iannetta Paul
2022-07-29  7:36     ` Marc Poulhies
2022-07-29  9:29       ` Thomas Schwinge
2022-07-29 12:34     ` Richard Earnshaw [this message]
2022-07-28 19:49 ` Tim Lange
2022-07-28 19:53   ` Jonathan Wakely
2022-08-01  8:24     ` Stefan Schulze Frielinghaus
2022-08-01 11:25       ` Jonathan Wakely
2022-08-01 12:16         ` Stefan Schulze Frielinghaus
2022-08-01 16:17           ` Jonathan Wakely
2022-08-01 10:50   ` Martin Liška

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=6388d619-97da-5acb-cac4-53e2119b4fed@foss.arm.com \
    --to=richard.earnshaw@foss.arm.com \
    --cc=amonakov@ispras.ru \
    --cc=gcc-bounces+paul.iannetta=ens-lyon.fr@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=paul.iannetta@ens-lyon.fr \
    /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).