Re: pgindent exit status if a file encounters an error - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: pgindent exit status if a file encounters an error
Date
Msg-id 7a6b4715-a7e0-4476-9d9d-6c7c59ca9466@dunslane.net
Whole thread Raw
In response to Re: pgindent exit status if a file encounters an error  (Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>)
Responses Re: pgindent exit status if a file encounters an error
List pgsql-hackers


On 2024-06-28 Fr 8:35 AM, Ashutosh Bapat wrote:


On Wed, Jun 26, 2024 at 8:54 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
Ashutosh Bapat <ashutosh.bapat.oss@gmail.com> writes:
> The usage help mentions exit code 2 specifically while describing --check
> option but it doesn't mention exit code 1. Neither does the README. So I
> don't think we need to document exit code 3 anywhere. Please let me know if
> you think otherwise.

I think we should have at least a code comment summarizing the
possible exit codes, along the lines of

# Exit codes:
#   0 -- all OK
#   1 -- could not invoke pgindent, nothing done
#   2 -- --check mode and at least one file requires changes
#   3 -- pgindent failed on at least one file

Thanks. Here's a patch with these lines.
 
In an offline chat Andrew mentioned that he expects more changes in the patch and he would take care of those. Will review and test his patch.



I forget now what I was intending here, so I have committed this with minor tweaks.


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com

pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: ecpg command does not warn COPY ... FROM STDIN;
Next
From: Peter Eisentraut
Date:
Subject: Re: Virtual generated columns