Re: [HACKERS] proposal: psql: check env variable PSQL_PAGER - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: [HACKERS] proposal: psql: check env variable PSQL_PAGER
Date
Msg-id CAEepm=3_HyK=BVeFQzw80i+64iXVY8WfODZ3uxuk3N0K4QdDtA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] proposal: psql: check env variable PSQL_PAGER  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: [HACKERS] proposal: psql: check env variable PSQL_PAGER  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
On Thu, Jul 27, 2017 at 4:19 AM, Pavel Stehule <pavel.stehule@gmail.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
usingpager-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



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: [HACKERS] taking stdbool.h into use
Next
From: Amit Langote
Date:
Subject: Re: [HACKERS] expanding inheritance in partition bound order