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 08:03:51
Message-ID: 20230907.170351.1552864966311860985.horikyota.ntt@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

At Thu, 7 Sep 2023 16:08:10 +0900, Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp> wrote in
> On Thu, 07 Sep 2023 15:36:10 +0900 (JST)
> Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote:
>
> > At Thu, 7 Sep 2023 15:02:49 +0900, Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp> wrote in
> > > 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:
>
> Yes. So, I mean how about fixing \watch description as the attached patch.

Ah. I see. I thought you meant that line needed the same change.

> >
> > > \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

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2023-09-07 08:04:41 Re: [BackendXidGetPid] only access allProcs when xid matches
Previous Message Bagga, Rishu 2023-09-07 08:03:16 Re: SLRUs in the main buffer pool - Page Header definitions