Re: psql help message contains excessive indentations

From: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
To: nagata(at)sraoss(dot)co(dot)jp
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: psql help message contains excessive indentations
Date: 2023-09-07 06:36:10
Message-ID: 20230907.153610.2165693466762464599.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Thu, 7 Sep 2023 15:02:49 +0900, Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp> wrote in
> On Thu, 07 Sep 2023 14:29:56 +0900 (JST)
> Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote:
> > > \q quit psql
> > > \watch [[i=]SEC] [c=N] [m=MIN]
> > !> execute query every SEC seconds, up to N times
> > !> stop if less than MIN rows are returned
> >
> > The last two lines definitely have some extra indentation.
>
> Agreed.
>
> > I've attached a patch that fixes this.
>
> I wonder this better to fix this in similar way to other places where the
> description has multiple lines., like "\g [(OPTIONS)] [FILE]".

It looks correct to me:

> \errverbose show most recent error message at maximum verbosity
> \g [(OPTIONS)] [FILE] execute query (and send result to file or |pipe);
> \g with no arguments is equivalent to a semicolon
> \gdesc describe result of query, without executing it

regards.

--
Kyotaro Horiguchi
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2023-09-07 06:43:15 Re: [PoC] Reducing planning time when tables have many partitions
Previous Message Michael Paquier 2023-09-07 06:33:58 Re: pg_upgrade and logical replication