Re: wrapping in extended mode doesn't work well with default pager

From: Greg Stark <stark(at)mit(dot)edu>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Emre Hasegeli <emre(at)hasegeli(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Sergey Muraviov <sergey(dot)k(dot)muraviov(at)gmail(dot)com>
Subject: Re: wrapping in extended mode doesn't work well with default pager
Date: 2014-05-12 13:12:01
Message-ID: CAM-w4HMxrVgSrUH1UUGYMkA0bf7FVbA-x6jKrtLPm1x+6bYq4A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, May 12, 2014 at 2:00 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> but where did those leading spaces come from? The header line is
> definitely not on board with that, and I think those spaces are
> contributing to the lines being too long for the window. I think
> possibly the code is also adding a space that shouldn't be there
> at the end of the lines, because it prints lines that wrap around
> if I \pset columns to either 79 or 80 in an 80-column window, so
> the accounting is off by 2 someplace.

Hm, there was an off by one error earlier in some cases, maybe we
fixed it by breaking other case. Will investigate.

--
greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2014-05-12 13:15:55 Re: pgaudit - an auditing extension for PostgreSQL
Previous Message Tom Lane 2014-05-12 13:00:16 Re: wrapping in extended mode doesn't work well with default pager