From: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Questions about proper newline handling in psql output |
Date: | 2005-09-27 00:12:15 |
Message-ID: | e7a60c3c74141f6d7cdff6c96a994df9@biglumber.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> 3. How to show that a value is continued? As you can see below I use
>...
> I remember a discussion on this before but couldn't find it in the
> archives. Either a reference or some other hints would be appreciated.
I think we liked the "+" character.
> 4. Some system output like pg_views has really really long strings,
> would it be acceptable to change the output there to add newlines at
> various places to make it output nicer with this change?
I'd say no, until you propose a more concrete set of rules on how and when.
> 5. Auto string folding. If a string is really long, fold it so it fits
> in a screen width, perhaps with '\' continuation. I havn't done this
> but I can imagine some people (including me) would love it.
Sounds good to me.
> Query is: select oid, prosrc as "HdrLine1 HdrLine2", proacl from pg_proc limit 1;
Some smaller samples with a third column (and a large 2nd one) might be nice.
Thanks for tackling this, it should be a nice improvement.
- --
Greg Sabino Mullane greg(at)turnstep(dot)com
PGP Key: 0x14964AC8 200509262011
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----
iD8DBQFDOI5OvJuQZxSWSsgRAoiZAJ4sNyNMFE5+xiA+uDlRnWZA03cbmACfWv67
lFKR/iwZnkp7mb0BvLLFkkk=
=L9nw
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-09-27 00:12:37 | Making pgxs builds work with a relocated installation |
Previous Message | Marc G. Fournier | 2005-09-27 00:01:31 | Re: State of support for back PG branches |