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

From Pavel Stehule
Subject Re: new unicode table border styles for psql
Date
Msg-id CAFj8pRDkzN63d20tc-x6vbCgxOBhnZZBwfrN6MXNX=f3gxhRpg@mail.gmail.com
Whole thread Raw
In response to Re: new unicode table border styles for psql  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: new unicode table border styles for psql  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
List pgsql-hackers



2013/11/22 Merlin Moncure <mmoncure@gmail.com>
On Fri, Nov 22, 2013 at 2:23 AM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
> Hello
>
>
> 2013/11/21 Merlin Moncure <mmoncure@gmail.com>
>>
>> On Thu, Nov 21, 2013 at 1:09 AM, Pavel Stehule <pavel.stehule@gmail.com>
>> wrote:
>> > Hello
>> >
>> > I wrote new styles for  psql table borders.
>> >
>> > http://postgres.cz/wiki/Pretty_borders_in_psql
>> >
>> > This patch is simply and I am think so some styles can be interesting
>> > for
>> > final presentation.
>> >
>> great. hm, maybe we could integrate color? (see:
>>
>> http://merlinmoncure.blogspot.com/2012/09/psql-now-with-splash-of-color.html).
>
>
> it is next possible enhancing - I would to go forward in small steps, please
> :)
>
> minimally (and independent on proposed patch) we can introduce some like
> "final regexp filtering"  - that can be used for this or other purposes.

Yeah.  A per field regexp would do the trick.  As you have it, I like
Peter's idea best.  Being able to specify the various character codes
makes a lot of sense.

there is other issue - simply parser will be really user unfriendly, and user friendly parser will not by simply :(

have you some idea about input format?

Regards

Pavel
 

merlin

pgsql-hackers by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: new unicode table border styles for psql
Next
From: Tom Lane
Date:
Subject: Re: address sanitizer crash