| From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgindent to ignore build directories |
| Date: | 2026-09-28 03:42:04 |
| Message-ID: | CAGECzQS_vv5ixC4AmaOoffqgk1D+3QW9Ugw=Tzd=8ND_CFw7uw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 28 Sept 2026 at 05:25, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> And even if it
> prints just what you need to know on stderr, that's transient data
> that has probably scrolled off your terminal window by the time you
> finished with the first problem.
That seems easily solved by piping stderr to a file (e.g. using tee):
src/tools/pgindent/pgindent . 2>| tee pgindent-errors.log
Another option is to simply rerun pgindent again after fixing a file
to get the rest of the failing files.
I'm personally much more annoyed by a bunch of random garbage files
being created in my working directory than by having to do either of
those when I want to run pgindent on my full tree.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | solai v | 2026-09-28 04:34:00 | Re: NOT NULL NOT ENFORCED |
| Previous Message | Michael Paquier | 2026-09-28 03:38:05 | Re: Translation of the NextOID message in pg_controldata |