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

2022-08-01 Thread Jonathan Wakely via Gcc
On Mon, 1 Aug 2022 at 13:16, Stefan Schulze Frielinghaus wrote: > > On Mon, Aug 01, 2022 at 12:25:21PM +0100, Jonathan Wakely wrote: > > On Mon, 1 Aug 2022 at 09:24, Stefan Schulze Frielinghaus wrote: > > > I gave unexpand from GNU coreutils 8.32 a try. Looks like it cannot > > > deal with form

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

2022-08-01 Thread Stefan Schulze Frielinghaus via Gcc
On Mon, Aug 01, 2022 at 12:25:21PM +0100, Jonathan Wakely wrote: > On Mon, 1 Aug 2022 at 09:24, Stefan Schulze Frielinghaus wrote: > > I gave unexpand from GNU coreutils 8.32 a try. Looks like it cannot > > deal with form feeds or maybe I'm missing something? > > > > $ bash -c "printf 'foo\n\f\n

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

2022-08-01 Thread Jonathan Wakely via Gcc
On Mon, 1 Aug 2022 at 09:24, Stefan Schulze Frielinghaus wrote: > I gave unexpand from GNU coreutils 8.32 a try. Looks like it cannot > deal with form feeds or maybe I'm missing something? > > $ bash -c "printf 'foo\n\f\nbar\n'" | unexpand - > foo > unexpand: input line is too long Which

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

2022-08-01 Thread Martin Liška
On 7/28/22 21:49, Tim Lange wrote: > > > On Thu, Jul 28 2022 at 02:46:58 PM -0400, 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

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

2022-08-01 Thread Stefan Schulze Frielinghaus via Gcc
On Thu, Jul 28, 2022 at 08:53:37PM +0100, Jonathan Wakely via Gcc wrote: > On Thu, 28 Jul 2022 at 20:49, Tim Lange wrote: > > > > > > > > On Thu, Jul 28 2022 at 02:46:58 PM -0400, David Malcolm via Gcc > > wrote: > > > Is there documentation on setting up text editors to work with our > > >

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

2022-07-29 Thread Richard Earnshaw via Gcc
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

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

2022-07-29 Thread Thomas Schwinge
Hi! On 2022-07-29T09:36:41+0200, Marc Poulhies via Gcc wrote: > Iannetta Paul 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. > >

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

2022-07-29 Thread Thomas Schwinge
Hi! On 2022-07-29T09:36:41+0200, Marc Poulhies via Gcc wrote: > Iannetta Paul 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. > >

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

2022-07-29 Thread Marc Poulhies via Gcc
Iannetta Paul writes: Hi Paul :) > 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

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

2022-07-28 Thread Iannetta Paul
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

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

2022-07-28 Thread Jonathan Wakely via Gcc
On Thu, 28 Jul 2022 at 20:49, Tim Lange wrote: > > > > On Thu, Jul 28 2022 at 02:46:58 PM -0400, 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

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

2022-07-28 Thread Tim Lange
On Thu, Jul 28 2022 at 02:46:58 PM -0400, 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

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

2022-07-28 Thread Alexander Monakov via Gcc
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

Setting up editors for the GNU/GCC coding style?

2022-07-28 Thread David Malcolm via Gcc
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