Re: \l of psql 8.4 looks ... unreadable on 80char default

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: Harald Armin Massa <haraldarminmassa(at)gmail(dot)com>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, General Postgres Mailing List <pgsql-general(at)postgresql(dot)org>
Subject: Re: \l of psql 8.4 looks ... unreadable on 80char default
Date: 2009-02-19 14:36:57
Message-ID: 87zlgi4ho6.fsf@oxford.xeocode.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Harald Armin Massa <haraldarminmassa(at)gmail(dot)com> writes:

> Thanks!
>
>> What is your $COLUMNS set to? This should have wrapped to fit into the
>> screen with. Also look at \pset columns:
>
> $COLUMNS was not set at all ... guess that is a usual environment
> variable on bash. Setting it to 80 works.

COLUMNS wasn't set and \pset columns wasn't set? What environment were you
running this psql command in? Was the output redirected anywhere with \o or
with > on the commandline?

We had a long argument about how this should work a while back so I suspect
people aren't psyched about reopening it, but while I don't think the current
logic is right I don't think wrapping to 80 columns when your terminal is
wider is one of the current broken cases. It tends to fail in the opposite
direction of randomly not wrapping at all so it's kind of surprising to see
your experience.

--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
Get trained by Bruce Momjian - ask me about EnterpriseDB's PostgreSQL training!

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Craig Ringer 2009-02-19 14:46:09 Re: postgres wish list
Previous Message Chander Ganesan 2009-02-19 14:04:01 Re: postgres wish list