Re: proposal: psql: check env variable PSQL_PAGER

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Thomas Munro <thomas(dot)munro(at)enterprisedb(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 09:56:05
Message-ID: CAFj8pRCJS+gcJS2MH+L6H-P1j0i-njR+xBdFuxHT6N9NaCSirA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

Hi

2017-08-16 6:58 GMT+02:00 Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>:

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

I am not sure if I see last issue well. Sending updated patch

Regards

Pavel

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

Attachment Content-Type Size
psql-psql-pager-env-2.patch text/x-patch 2.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrey Borodin 2017-08-16 09:58:08 Re: GSoC 2017 : Patch for predicate locking in Gist index
Previous Message Heikki Linnakangas 2017-08-16 09:28:20 Re: [PATCH] Remove unused argument in btree_xlog_split