| From: | John Naylor <johncnaylorls(at)gmail(dot)com> |
|---|---|
| To: | Tristan Partin <tristan(at)neon(dot)tech> |
| Cc: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Add BF member koel-like indentation checks to SanityCheck CI |
| Date: | 2024-01-10 06:14:25 |
| Message-ID: | CANWCAZa6zO8FNzDCXdMBwwBo0csvWCcOJ12Np-11G42VPUTk4g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 10, 2024 at 2:20 AM Tristan Partin <tristan(at)neon(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sutou Kouhei | 2024-01-10 06:20:23 | Re: Make COPY format extendable: Extract COPY TO format implementations |
| Previous Message | Tom Lane | 2024-01-10 06:13:57 | Re: Make NUM_XLOGINSERT_LOCKS configurable |