| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Christoph Berg <myon(at)debian(dot)org>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Platon Pronko <platon7pronko(at)gmail(dot)com>, Zhihong Yu <zyu(at)yugabyte(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: \pset xheader_width page as default? (Re: very long record lines in expanded psql output) |
| Date: | 2022-08-30 14:49:57 |
| Message-ID: | CAFj8pRBehZU4jZMQ7NieunSG4xOgsQXh9_zDQtirpKOyJYdO3Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
út 30. 8. 2022 v 16:36 odesílatel Christoph Berg <myon(at)debian(dot)org> napsal:
> Re: Pavel Stehule
> > pspg requires all lines to have the same width. It can do some
> corrections
> > - but it is hard to detect wanted differences or just plain text format.
> >
> > can be nice to have the first invisible row with some information about
> > used formatting. pspg does some heuristic but this code is not nice and
> it
> > is fragile.
>
> I like pspg and use it myself, but I don't think a tool that does the
> right thing by hiding a full screen of ---- from the user should
> hinder making the same progress in psql with a simple pager.
>
ASCII allows to set some metadata, that should be invisible in all
correctly implemented pagers.
>
> Christoph
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2022-08-30 14:52:51 | Re: Convert *GetDatum() and DatumGet*() macros to inline functions |
| Previous Message | Christoph Berg | 2022-08-30 14:36:49 | Re: \pset xheader_width page as default? (Re: very long record lines in expanded psql output) |