From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | "D'Arcy J(dot)M(dot) Cain" <darcy(at)druid(dot)net> |
Cc: | Greg Smith <gsmith(at)gregsmith(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Proposal: new border setting in psql |
Date: | 2009-01-08 21:42:41 |
Message-ID: | 200901082142.n08LgfB17982@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
D'Arcy J.M. Cain wrote:
> The problem with escaping is that someone may want this output for
> non-ReST purposes. They may not be making themselves known now but if
> we find a need later it will be hard if not impossible to make it
> available in a logical way. I would suggest that if we want actual
> ReST-safe output we should create a "border = 4" setting. The code
> changes would be minimal. All we need to do is check for a value of 4
> in addition to checking whether escaping is necessary.
>
> I would still like to see some sort of plugin system for psql that
> would allow filters to be created for output. That would make this
> entire discussion moot as each of us could write whatever filter worked
> for them. That's a bigger deal though.
Well, the way we do Html and LaTeX now is:
\pset format {html|latex}
so I assume ReST would be:
\pset format {html|latex|rest}
You can implement the user-visible, no-escaping version of ReST by using
border=3.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2009-01-08 21:48:46 | Re: Buffer pool statistics in Explain Analyze |
Previous Message | Bruce Momjian | 2009-01-08 21:39:40 | Improving compressibility of WAL files |