From: Alexander Monakov <amonakov@ispras.ru>
To: David Malcolm <dmalcolm@redhat.com>
Cc: gcc@gcc.gnu.org
Subject: Re: Setting up editors for the GNU/GCC coding style?
Date: Thu, 28 Jul 2022 22:00:21 +0300 (MSK) [thread overview]
Message-ID: <fa8ed1f-c57f-277b-3261-cc41c9b3d0d6@ispras.ru> (raw)
In-Reply-To: <abd785fa4d39650d2d5b71157f81934b783e928d.camel@redhat.com>
On Thu, 28 Jul 2022, David Malcolm via Gcc wrote:
> Is there documentation on setting up text editors to work with our
> coding style? A lot of the next generation of developers aren't using
> vi or emacs; they's using VS Code, CLion, and other editors. Does
> anyone have docs on e.g. how to set up VS Code, CLion, etc (IntelliJ ?)
> to work well on GCC's own code base. FWIW I use Emacs; I've dabbed
> with VS Code but haven't used it "for real".
>
> I'm hoping to add this to my newbies guide.
The tricky part is setting it up so it doesn't die indexing the codebase
(e.g. adding the entire toplevel directory probably won't work: it will
try to index the testsuites).
FWIW, CLion documentation shows how to select GNU coding style, but as
above, that's not the main worry:
https://www.jetbrains.com/help/clion/predefined-code-styles.html
Alexander
next prev parent reply other threads:[~2022-07-28 19:00 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 [this message]
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
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=fa8ed1f-c57f-277b-3261-cc41c9b3d0d6@ispras.ru \
--to=amonakov@ispras.ru \
--cc=dmalcolm@redhat.com \
--cc=gcc@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).