Re: Add BF member koel-like indentation checks to SanityCheck CI - Mailing list pgsql-hackers

From John Naylor
Subject Re: Add BF member koel-like indentation checks to SanityCheck CI
Date
Msg-id CANWCAZa6zO8FNzDCXdMBwwBo0csvWCcOJ12Np-11G42VPUTk4g@mail.gmail.com
Whole thread Raw
In response to Re: Add BF member koel-like indentation checks to SanityCheck CI  ("Tristan Partin" <tristan@neon.tech>)
Responses Re: Add BF member koel-like indentation checks to SanityCheck CI
List pgsql-hackers
On Wed, Jan 10, 2024 at 2:20 AM Tristan Partin <tristan@neon.tech> wrote:
>
> On Tue Jan 9, 2024 at 3:00 AM CST, John Naylor wrote:
> > I don't indent during most of development, and don't intend to start.
>
> Could you expand on why you don't? I could understand as you're writing,
> but I would think formatting on save, might be useful.

Off the top of my head, I like to use '//' comments as quick notes to
myself that stand out from normal code comments, and I'm in the habit
of putting debug print statements flush against the left margin so
they're really obvious. Both of these would be wiped out by pgindent.



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Make NUM_XLOGINSERT_LOCKS configurable
Next
From: Sutou Kouhei
Date:
Subject: Re: Make COPY format extendable: Extract COPY TO format implementations