Re: Setting up editors for the GNU/GCC coding style?

[Iannetta Paul <paul.iannetta@ens-lyon.fr>]

On 2022-07-28 21:00, Alexander Monakov via Gcc wrote:

> On Thu, 28 Jul 2022, David Malcolm via Gcc wrote:
> 
> 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

Unless I am mistaken, I don't think that modern editors have support for 
autotools based projects, so they won't even attempt indexing the files.

For the indexing, I produce a compile_commands.json file (recording only 
the files compiled by `make all', this includes auto-generated files 
such as config.h, and the insn-something.{h,c} files) with the help of 
https://github.com/gicmo/cdcc, this file is then picked up by the 
language server, which then provides nice autocompletion features.

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.

Paul