Re: proposal: psql: check env variable PSQL_PAGER

From: Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: proposal: psql: check env variable PSQL_PAGER
Date: 2017-08-16 04:58:04
Message-ID: CAEepm=3_HyK=BVeFQzw80i+64iXVY8WfODZ3uxuk3N0K4QdDtA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 27, 2017 at 4:19 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> here is a patch - it is trivial

The feature makes sense, follows an existing example (PSQL_EDITOR),
and works nicely.

is platform-dependent. Use of the pager can be disabled by setting
<envar>PAGER</envar> to empty, or by using pager-related options of

Maybe this should now say "... can be disabled by specifying an empty
string", since "... by setting PAGER to empty" isn't quite the full
story.

- the <command>\pset</command> command.
+ the <command>\pset</command> command. These variables are examined
+ in the order listed; the first that is set is used.
</para>
+

Stray blank line.

--
Thomas Munro
http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2017-08-16 05:36:15 Re: expanding inheritance in partition bound order
Previous Message Peter Eisentraut 2017-08-16 04:36:09 taking stdbool.h into use