From: | James Coleman <jtc331(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pgindent (probably my missing something obvious) |
Date: | 2023-07-04 01:41:10 |
Message-ID: | CAAaqYe8uK6axbdELscc--dD+Yd7rBvqmLPXCgkPF9n4VtY640A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jul 3, 2023 at 9:20 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> James Coleman <jtc331(at)gmail(dot)com> writes:
> > This is the first time I've run pgindent on my current machine, and it
> > doesn't seem to be making any modifications to source files. For
> > example this command:
>
> > ./src/tools/pgindent/pgindent src/backend/optimizer/path/allpaths.c
>
> > leaves the allpaths.c file unchanged despite my having some very long
> > function calls.
>
> "Long function calls" aren't necessarily something pgindent would
> change. Have you tried intentionally misindenting some lines?
>
> regards, tom lane
Hmm, yeah, that works.
My heuristic for what pgindent changes must be wrong. The long
function calls (and 'if' conditions) seem obviously out of place to my
eyes with the surrounding code. Does that mean the surrounding code
was just hand-prettified?
Thanks,
James Coleman
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2023-07-04 02:04:21 | Re: pgindent (probably my missing something obvious) |
Previous Message | Hayato Kuroda (Fujitsu) | 2023-07-04 01:30:56 | RE: [PGdocs] fix description for handling pf non-ASCII characters |