Re: new unicode table border styles for psql - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: new unicode table border styles for psql
Date
Msg-id 5294F1C3.9040200@gmx.net
Whole thread Raw
In response to Re: new unicode table border styles for psql  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: new unicode table border styles for psql  (Pavel Stehule <pavel.stehule@gmail.com>)
Re: new unicode table border styles for psql  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
On 11/22/13, 3:26 AM, Pavel Stehule wrote:
> website is related to patch for 9.3 (I add note there)
> 
> patch for 9.4 is fixed - and now with small doc

I think it would help if we considered the new border styles and the new
line styles separately.

I don't find the new border styles to be particularly useful.  They just
use up vertical screen space, which is usually more precious than
vertical space.  Is there a situation where you would find these styles
to be more useful than the existing ones?  Keep in mind that pset is
usually set permanently, so it wouldn't be practical to use a different
border style depending on how the query results shape up (like \x auto).

Now for the linestyles.  I can see how some of them are attractive, but
several of them have poor aesthetics, I think.  I don't see a reason to
accept 7 new styles just for fun.  If I had to choose, I'd consider
-double1 and -double4 to be acceptable.




pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: INSERT...ON DUPLICATE KEY LOCK FOR UPDATE
Next
From: David Johnston
Date:
Subject: Re: why semicolon after begin is not allowed in postgresql?