Re: controlling psql's use of the pager a bit more

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: controlling psql's use of the pager a bit more
Date: 2014-11-13 17:55:42
Message-ID: CAHyXU0xb9ae=ipBzJWiVAO4Z9a3YKhdtMdttU+z2GdjfYeD92w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Nov 13, 2014 at 11:39 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Thu, Nov 13, 2014 at 11:54 AM, David G Johnston
> <david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>>> Because I might be quite happy with 100 or 200 lines I can just scroll
>>> in my terminal's scroll buffer, but want to use the pager for more than
>>> that. This is useful especially if I want to scroll back and see the
>>> results from a query or two ago.
>>
>> +1
>
> +1 from me, too.

me three (as long as the current behaviors are not messed with and the
new stuff is 'opt in' somehow -- I also use the force quit option to
less).

merlin

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Johnston 2014-11-13 18:03:31 Re: controlling psql's use of the pager a bit more
Previous Message Peter Geoghegan 2014-11-13 17:50:28 Re: Doing better at HINTing an appropriate column within errorMissingColumn()