| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: psql PSQL_TABULAR_PAGER variable |
| Date: | 2019-04-18 15:58:13 |
| Message-ID: | 20190418155813.gpvp2zjr2m6dgkbn@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Apr 18, 2019 at 05:45:24PM +0200, Pavel Stehule wrote:
> čt 18. 4. 2019 v 15:51 odesílatel Bruce Momjian <bruce(at)momjian(dot)us> napsal:
> In testing pspg, it seems to work fine with tabular and \x-non-tabular
> data. Are you asking for a pager option that is only used for non-\x
> display? What do people want the non-pspg pager to do?
>
> My idea is following - pseudocode
>
> else /* for \h xxx */
Well, normal output and \x looks fine in pspg, and \h doesn't use the
pager unless it is more than one screen. If I do '\h *' it uses pspg,
but now often do people do that? Most \h display doesn't use a pager,
so I don't see the point.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2019-04-18 16:06:40 | Re: proposal: psql PSQL_TABULAR_PAGER variable |
| Previous Message | Pavel Stehule | 2019-04-18 15:45:24 | Re: proposal: psql PSQL_TABULAR_PAGER variable |