From: | Joe Conway <mail(at)joeconway(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_regress help output |
Date: | 2017-10-11 02:31:21 |
Message-ID: | cef160b9-0ff5-dcdf-69c4-d9df55639784@joeconway.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10/10/2017 07:06 PM, Tom Lane wrote:
> Joe Conway <mail(at)joeconway(dot)com> writes:
>> I have been annoyed at least twice now by the lack of pg_regress command
>> line help output for the "--bindir=<path>" option. In passing I noted
>> that there was no output for "--help" or "--version" options either.
>
>> Any objections to the attached?
>
> +1 for documenting it, but the phrasing seems a bit awkward:
>
> ! printf(_(" --bindir=BINPATH use BINPATH for programs that are run;\n"));
> ! printf(_(" if BINPATH empty, use PATH from the environment\n"));
>
> Maybe just "if empty, use PATH ..." ?
Ok, so like this?
8<----------
--bindir=BINPATH use BINPATH for programs that are run;\n"));
if empty, use PATH from the environment\n"));
8<----------
> Also, why is the patch apparently changing whitespace in all the help
> lines? Seems like that will create a lot of make-work for translators.
I debated with myself about that.
In other cases, e.g. initdb or psql, where we mix short+long options and
long-only options, we indent the long-only options in the output to
match up with the long-options of the mixed lines (whew, hopefully that
is clear).
Previously we were not showing mixed short+long options for pg_regress
at all, and hence only indenting the long-only options minimally. But
the addition of -h and -V (again consistent with other programs we
ship), it made sense to be consistent in the way we indent.
But I am fine with leaving the original lines output the way they were
if preferred.
Joe
--
Crunchy Data - http://crunchydata.com
PostgreSQL Support for Secure Enterprises
Consulting, Training, & Open Source Development
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2017-10-11 02:35:20 | Re: [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple |
Previous Message | Wood, Dan | 2017-10-11 02:31:13 | Re: [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple |