public inbox for [email protected]
help / color / mirror / Atom feedFrom: John Naylor <[email protected]>
To: Tristan Partin <[email protected]>
Cc: Bharath Rupireddy <[email protected]>
Cc: Jelte Fennema-Nio <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Subject: Re: Add BF member koel-like indentation checks to SanityCheck CI
Date: Wed, 10 Jan 2024 13:14:25 +0700
Message-ID: <CANWCAZa6zO8FNzDCXdMBwwBo0csvWCcOJ12Np-11G42VPUTk4g@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CALj2ACWMupLTuD+bWfr2oBsNDpFJiuFaCK17S3Ty0YJbywdSfA@mail.gmail.com>
<CANWCAZZObZeN9VqgmMY+mk4F1kpkuj=JB65R+o_HHoFT8c+eKg@mail.gmail.com>
<[email protected]>
On Wed, Jan 10, 2024 at 2:20 AM Tristan Partin <[email protected]> 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.
view thread (5+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: Add BF member koel-like indentation checks to SanityCheck CI
In-Reply-To: <CANWCAZa6zO8FNzDCXdMBwwBo0csvWCcOJ12Np-11G42VPUTk4g@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox