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

Gregory,

>> $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?

Environment: cmd.exe within Windows 7 Beta 64bit.
(should be quite similar to Vista & XP)

And I did not redirect anything ... Just started a default cmd.exe, to
paste it into the email I used "select" and "copy" from the
system-menu of that window.

(this "\l" is just my "ritual" after installing PostgreSQL, to see
that PostgreSQL is installed and the installer accepted my wish for
UTF-8)

> 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.

It did not wrap at all, so that "randomly not wrapping at all" was my
kind of failure, wasn't it?

Harald

--
GHUM Harald Massa
persuadere et programmare
Harald Armin Massa
Spielberger Straße 49
70435 Stuttgart
0173/9409607
no fx, no carrier pigeon
-
EuroPython 2009 will take place in Birmingham - Stay tuned!