pgsql: Improve psql's tabular display of wrapped-around data by

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Improve psql's tabular display of wrapped-around data by
Date: 2009-11-22 05:20:41
Message-ID: 20091122052041.F08E0753FB7@cvs.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Log Message:
-----------
Improve psql's tabular display of wrapped-around data by inserting markers
in the formerly-always-blank columns just to left and right of the data.
Different marking is used for a line break caused by a newline in the data
than for a straight wraparound. A newline break is signaled by a "+" in the
right margin column in ASCII mode, or a carriage return arrow in UNICODE mode.
Wraparound is signaled by a dot in the right margin as well as the following
left margin in ASCII mode, or an ellipsis symbol in the same places in UNICODE
mode. "\pset linestyle old-ascii" is added to make the previous behavior
available if anyone really wants it.

In passing, this commit also cleans up a few regression test files that
had unintended spacing differences from the current actual output.

Roger Leigh, reviewed by Gabrielle Roth and other members of PDXPUG.

Modified Files:
--------------
pgsql/contrib/dblink/expected:
dblink.out (r1.26 -> r1.27)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/dblink/expected/dblink.out?r1=1.26&r2=1.27)
pgsql/contrib/pgcrypto/expected:
crypt-blowfish.out (r1.3 -> r1.4)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/expected/crypt-blowfish.out?r1=1.3&r2=1.4)
pgp-armor.out (r1.4 -> r1.5)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/expected/pgp-armor.out?r1=1.4&r2=1.5)
pgp-decrypt.out (r1.1 -> r1.2)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/pgcrypto/expected/pgp-decrypt.out?r1=1.1&r2=1.2)
pgsql/contrib/tsearch2/expected:
tsearch2.out (r1.28 -> r1.29)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/tsearch2/expected/tsearch2.out?r1=1.28&r2=1.29)
tsearch2_1.out (r1.1 -> r1.2)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/tsearch2/expected/tsearch2_1.out?r1=1.1&r2=1.2)
pgsql/doc/src/sgml/ref:
psql-ref.sgml (r1.232 -> r1.233)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/psql-ref.sgml?r1=1.232&r2=1.233)
pgsql/src/bin/psql:
command.c (r1.210 -> r1.211)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/command.c?r1=1.210&r2=1.211)
print.c (r1.117 -> r1.118)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/print.c?r1=1.117&r2=1.118)
print.h (r1.41 -> r1.42)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/bin/psql/print.h?r1=1.41&r2=1.42)
pgsql/src/test/regress/expected:
create_cast.out (r1.1 -> r1.2)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/create_cast.out?r1=1.1&r2=1.2)
dependency.out (r1.9 -> r1.10)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/dependency.out?r1=1.9&r2=1.10)
foreign_data.out (r1.10 -> r1.11)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/foreign_data.out?r1=1.10&r2=1.11)
foreign_key.out (r1.48 -> r1.49)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/foreign_key.out?r1=1.48&r2=1.49)
guc.out (r1.8 -> r1.9)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/guc.out?r1=1.8&r2=1.9)
prepare.out (r1.19 -> r1.20)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/prepare.out?r1=1.19&r2=1.20)
triggers.out (r1.29 -> r1.30)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/triggers.out?r1=1.29&r2=1.30)
tsearch.out (r1.16 -> r1.17)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/tsearch.out?r1=1.16&r2=1.17)
with.out (r1.12 -> r1.13)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/src/test/regress/expected/with.out?r1=1.12&r2=1.13)

Browse pgsql-committers by date

  From Date Subject
Next Message User Okbob 2009-11-22 05:59:25 orafce - orafce: add support for dbms_random (skeleton only)
Previous Message Peter Eisentraut 2009-11-21 23:59:12 pgsql: Ignore UTF-8-encoded Unicode byte-order mark at the beginning of