Re: Markdown format output for psql, design notes

2018-12-02 Thread Lætitia Avrot
If I sum it up, we're at 2 against trying to write such a patch and one for (with some modifications about which markdown format to implement). Anyone else wants to join the vote? Cheers, Lætitia Le dim. 2 déc. 2018 à 05:11, Pavel Stehule a écrit : > > > so 1. 12. 2018 v 22:11 odesílatel

Re: Markdown format output for psql, design notes

2018-12-01 Thread Pavel Stehule
so 1. 12. 2018 v 22:11 odesílatel Daniel Verite napsal: > Lætitia Avrot wrote: > > > But as Vik said earlier, maybe it's not worth it to provide a markdown > > output as pandoc can generate the markdown from the HTML output. > > And if you need the markdown output to generate HTML why

Re: Markdown format output for psql, design notes

2018-12-01 Thread Daniel Verite
Lætitia Avrot wrote: > But as Vik said earlier, maybe it's not worth it to provide a markdown > output as pandoc can generate the markdown from the HTML output. > And if you need the markdown output to generate HTML why don't you use the > HTML output ? The round-trip through pandoc does

Re: Markdown format output for psql, design notes

2018-11-30 Thread Lætitia Avrot
Hi, No I meant independently of the screen, if there's an LF character > in a cell. Or a '|' character, since that's the same problem: an > element of structure happening to be in the contents. > The specs mentioned upthread don't seem to give any indication > about that being supported. > > i've

Re: Markdown format output for psql, design notes

2018-11-29 Thread Vik Fearing
On 29/11/2018 08:26, Lætitia Avrot wrote: > # What stays in my mind > > * It's pretty difficult to handle line breaks > * Markdown is not standardised and several flavours exist for table > implementation (so why favor one over the others?) > > # The question I'd like to ask you > So now, I

Re: Markdown format output for psql, design notes

2018-11-29 Thread Daniel Verite
Lætitia Avrot wrote: > I suppose you mean in the standard output when the screen is too short to > print the whole line ? > Because if the output is redirected to a file (with `\o myfile` for > example), the line end naturally when the row ends. No I meant independently of the screen, if

Re: Markdown format output for psql, design notes

2018-11-28 Thread Lætitia Avrot
> > I'm a little bit reluctant for us to write and maintain more and more > format styles, especially one as subjective and varied as markdown. I > imagine we will constantly be bombarded with "this isn't quite right" or > "this isn't compatible with github". > > I understand your concern. It's a

Re: Markdown format output for psql, design notes

2018-11-28 Thread Lætitia Avrot
Le mer. 28 nov. 2018 à 16:25, Daniel Verite a écrit : > Lætitia Avrot wrote: > > > # The result I want > > From points 3 and 4, here is what I'd like to see : > > > > | Header 1 | Header 2 | Header 3 | > > |--|--|--| > > | content | content | content | > > |

Re: Markdown format output for psql, design notes

2018-11-28 Thread Daniel Verite
Lætitia Avrot wrote: > # The result I want > From points 3 and 4, here is what I'd like to see : > > | Header 1 | Header 2 | Header 3 | > |--|--|--| > | content | content | content | > | content | content | content | > (2 rows) What would it look like when a

Re: Markdown format output for psql, design notes

2018-11-28 Thread Pavel Stehule
st 28. 11. 2018 v 9:59 odesílatel Lætitia Avrot napsal: > Hi all, > > # What I'd like to do > I've been working on the idea of a markdown format for psql as I had said > in that thread : >

Markdown format output for psql, design notes

2018-11-28 Thread Lætitia Avrot
Hi all, # What I'd like to do I've been working on the idea of a markdown format for psql as I had said in that thread : https://www.postgresql.org/message-id/flat/CAB_COdiiwTmBcrmjXWCKiqkcPgf_bLodrUyb4GYE6pfKeoK2eg%40mail.gmail.com An attempt was made a year ago (see here :