From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bryce Nesbitt <bryce2(at)obviously(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: psql wrapped format default for backslash-d commands |
Date: | 2008-05-13 18:33:37 |
Message-ID: | 200805131833.m4DIXbq26722@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera wrote:
> There's another serious usability problem here, which is that the pager
> ability is not being used correctly. Consider the \df+ tg_* query I
> used as example for another bug report. psql says that it is 27 rows; I
> have my window taller than that (47 lines right now), yet the output is
> actually *a lot* longer than 27 rows (598 lines), due to the embedded
> newlines in the functions source. Yet the pager is not used, and so the
> whole thing scrolls past.
Yes, I mentioned that as a known bug, but when we exceed the screen
width and wrap over we don't adjust the pager either, so I figured it
was OK.
> Also: someone else said that if the pager mode is "auto", then the pager
> should be used not only when the output is _longer_ than the screen, but
> also if it's _wider_. I agree with that.
Hmmm, we could do that. Though remember the 'pager' variable is
confusing; automatic is 'on', and 'always' is always. Changing that to
'on/auto/off' was a suggestion I just made, and doing the same for
expanded.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Decibel! | 2008-05-14 00:20:27 | Re: Syntax decisions for pl/pgsql RAISE extension |
Previous Message | Alvaro Herrera | 2008-05-13 18:19:16 | Re: psql wrapped format default for backslash-d commands |