On Wed, Ju= n 24, 2015 at 06:11:20PM -0400, David G. Johnston wrote:
> http://www.postgresql.org/docs/devel/s= tatic/app-psql.html
>
> The other pset keywords with black-slash aliases include a "(or &= lt;letter>)"
> paren after the keyword. =C2=A0"title" does not (should be &= quot;C")

Attached is a patch to implement this, including a doc patch.

=E2=80=8BWasn't expecting a code = change - just the docs.=C2=A0 The docs already said the "\C [ title ]&= quot; is a valid meta-command...

Did you maybe end up making a command line &= quot;-C 'title'" valid instead?

David J.

--001a113ec43010d6e1051e420a3a-- From bruce@momjian.us Sun May 24 04:56:28 2026 Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZUysh-0005nP-MD for pgsql-docs@arkaria.postgresql.org; Thu, 27 Aug 2015 15:14:23 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZUysh-0008Ib-8h for pgsql-docs@arkaria.postgresql.org; Thu, 27 Aug 2015 15:14:23 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZUysL-0007WO-El for pgsql-docs@postgresql.org; Thu, 27 Aug 2015 15:14:01 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1ZUysE-0005GN-K2 for pgsql-docs@postgresql.org; Thu, 27 Aug 2015 15:14:00 +0000 Received: from bruce by momjian.us with local (Exim 4.72) (envelope-from ) id 1ZUysC-0007Sv-Bv; Thu, 27 Aug 2015 11:13:52 -0400 Date: Thu, 27 Aug 2015 11:13:52 -0400 From: Bruce Momjian To: "David G. Johnston" Cc: "pgsql-docs@postgresql.org" Subject: Re: Omission of "(or C)" in psql's "pset title" header Message-ID: <20150827151352.GJ29674@momjian.us> References: <20150827020226.GG29674@momjian.us> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-Pg-Spam-Score: -3.3 (---) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org On Wed, Aug 26, 2015 at 10:51:09PM -0400, David G. Johnston wrote: > On Wed, Aug 26, 2015 at 10:02 PM, Bruce Momjian wrote: > > On Wed, Jun 24, 2015 at 06:11:20PM -0400, David G. Johnston wrote: > > http://www.postgresql.org/docs/devel/static/app-psql.html > > > > The other pset keywords with black-slash aliases include a "(or ) > " > > paren after the keyword. "title" does not (should be "C") > > Attached is a patch to implement this, including a doc patch. > > > > Wasn't expecting a code change - just the docs. The docs already said the "\C > [ title ]" is a valid meta-command... > > Did you maybe end up making a command line "-C 'title'" valid instead? Obviously I am not understanding you. I thought you were looking for \pset C to be documented, and to work: test=> \pset C test Title is "test". That does not work in the current sources, so I had to add it. This is similar to how "\pset t" works as an alias for "\pset tuples_only": test=> \pset t Tuples only is on. When our docs say: tuples_only (or t) it is not talking about using \t, but rather "\pset t" --- perhaps that is where the confusion is coming from. (Yeah, I know it is kind of odd.) -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. + -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs From david.g.johnston@gmail.com Sun May 24 04:56:28 2026 Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZUzSA-0007F8-9t for pgsql-docs@arkaria.postgresql.org; Thu, 27 Aug 2015 15:51:02 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZUzS9-000638-Lj for pgsql-docs@arkaria.postgresql.org; Thu, 27 Aug 2015 15:51:01 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZUzS8-00062k-VN for pgsql-docs@postgresql.org; Thu, 27 Aug 2015 15:51:01 +0000 Received: from mail-io0-x22c.google.com ([2607:f8b0:4001:c06::22c]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1ZUzS4-00062u-3z for pgsql-docs@postgresql.org; Thu, 27 Aug 2015 15:51:00 +0000 Received: by iodb91 with SMTP id b91so61805656iod.1 for ; Thu, 27 Aug 2015 08:50:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=5/PKvxWthSbU4I2jRMM1esVKlJtWVvyC4sWWuqfKrw0=; b=DaKCY4h5UY83MOH6LwwTpRKWh2adl/aQO9DIw86yq2Zg+/+bB0zjPl3YXgyuRvqywJ rTiMXr27AMxKQuy8kb0h+pAlFkxeTN15LrUsT+JCPL5OW/xbD+wfwQHmt9dbZoGN89+r YzX51EV/9p4CHeyNxMrfMXMPRqbpvjD5BRmecqvm5Olc6nx17cWXptdx4W6rIPRTleV5 DT1tr7UmW3ofeBlUXRbmRRm+AuEGk2MSdYwinxxo/9A3z80xnrBVyZr+Gni6UjNhJPpe XUKdzJKy+UQ/vX3BlVtcEtrBgXbz6jUtv6nGtOCzdFjoliCLx+QqVZdP3Kx6UOn5t3nL xdhQ== MIME-Version: 1.0 X-Received: by 10.107.6.230 with SMTP id f99mr9724929ioi.61.1440690653866; Thu, 27 Aug 2015 08:50:53 -0700 (PDT) Received: by 10.36.143.141 with HTTP; Thu, 27 Aug 2015 08:50:53 -0700 (PDT) In-Reply-To: <20150827151352.GJ29674@momjian.us> References: <20150827020226.GG29674@momjian.us> <20150827151352.GJ29674@momjian.us> Date: Thu, 27 Aug 2015 11:50:53 -0400 Message-ID: Subject: Re: Omission of "(or C)" in psql's "pset title" header From: "David G. Johnston" To: Bruce Momjian Cc: "pgsql-docs@postgresql.org" Content-Type: multipart/alternative; boundary=001a113ed852a7b04a051e4cee73 X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org --001a113ed852a7b04a051e4cee73 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, Aug 27, 2015 at 11:13 AM, Bruce Momjian wrote: > On Wed, Aug 26, 2015 at 10:51:09PM -0400, David G. Johnston wrote: > > On Wed, Aug 26, 2015 at 10:02 PM, Bruce Momjian > wrote: > > > > On Wed, Jun 24, 2015 at 06:11:20PM -0400, David G. Johnston wrote: > > > http://www.postgresql.org/docs/devel/static/app-psql.html > > > > > > The other pset keywords with black-slash aliases include a "(or > ) > > " > > > paren after the keyword. "title" does not (should be "C") > > > > Attached is a patch to implement this, including a doc patch. > > > > > > > > =E2=80=8BWasn't expecting a code change - just the docs. The docs alre= ady said > the "\C > > [ title ]" is a valid meta-command... > > > > Did you maybe end up making a command line "-C 'title'" valid instead? > > Obviously I am not understanding you. I thought you were looking for > \pset C to be documented, and to work: > > test=3D> \pset C test > Title is "test". > > That does not work in the current sources, so I had to add it. This is > similar to how "\pset t" works as an alias for "\pset tuples_only": > > test=3D> \pset t > Tuples only is on. > > When our docs say: > > tuples_only (or t) > > it is not talking about using \t, but rather "\pset t" --- perhaps that > is where the confusion is coming from. (Yeah, I know it is kind of > odd.) > > =E2=80=8BYes, I read that as "\pset tuples_only" and "\t" are alternate for= ms of the same thing =E2=80=8B and thought that "\pset title" and "\C" should be documented simi= larly. Making "\pset C " work doesn't seem like an improvement. David J. --001a113ed852a7b04a051e4cee73 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On Thu, Au= g 27, 2015 at 11:13 AM, Bruce Momjian <bruce@momjian.us> wrote:

On Wed, Au= g 26, 2015 at 10:51:09PM -0400, David G. Johnston wrote:
> On Wed, Aug 26, 2015 at 10:02 PM, Bruce Momjian <bruce@momjian.us> wrote:
>
>=C2=A0 =C2=A0 =C2=A0On Wed, Jun 24, 2015 at 06:11:20PM -0400, David G. = Johnston wrote:
>=C2=A0 =C2=A0 =C2=A0> http://www.pos= tgresql.org/docs/devel/static/app-psql.html
>=C2=A0 =C2=A0 =C2=A0>
>=C2=A0 =C2=A0 =C2=A0> The other pset keywords with black-slash alias= es include a "(or <letter>)
>=C2=A0 =C2=A0 =C2=A0"
>=C2=A0 =C2=A0 =C2=A0> paren after the keyword. =C2=A0"title&quo= t; does not (should be "C")
>
>=C2=A0 =C2=A0 =C2=A0Attached is a patch to implement this, including a = doc patch.
>
>
>
> =E2=80=8BWasn't expecting a code change - just the docs.=C2=A0 The= docs already said the "\C
> [ title ]" is a valid meta-command...
>
> Did you maybe end up making a command line "-C 'title'&qu= ot; valid instead?

Obviously I am not understanding you. I thought you were looking for=
\pset C to be documented, and to work:

=C2=A0 =C2=A0 =C2=A0 =C2=A0 test=3D> \pset C test
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Title is "test".

That does not work in the current sources, so I had to add it.=C2=A0 This i= s
similar to how "\pset t" works as an alias for "\pset tuples= _only":

=C2=A0 =C2=A0 =C2=A0 =C2=A0 test=3D> \pset t
=C2=A0 =C2=A0 =C2=A0 =C2=A0 Tuples only is on.

When our docs say:

=C2=A0 =C2=A0 <term><literal>tuples_only</literal> (or &l= t;literal>t</literal>)</term>

it is not talking about using \t, but rather "\pset t" --- perhap= s that
is where the confusion is coming from.=C2=A0 (Yeah, I know it is kind of odd.)

<= br>

=E2=80=8BYes, I read that as "\pset tu= ples_only" and "\t" are alternate forms of the same thing

=E2=80=8B and thought that "\pset title" and= "\C" should be documented similarly.=C2=A0 Making "\pset C = <label>" work doesn't seem like an improvement.

<= div>

David J.

--001a113ed852a7b04a051e4cee73-- From bruce@momjian.us Sun May 24 04:56:28 2026 Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZUzhX-0007pw-NI for pgsql-docs@arkaria.postgresql.org; Thu, 27 Aug 2015 16:06:55 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZUzhX-0003LN-9L for pgsql-docs@arkaria.postgresql.org; Thu, 27 Aug 2015 16:06:55 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZUzhB-0002Se-DA for pgsql-docs@postgresql.org; Thu, 27 Aug 2015 16:06:33 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1ZUzh8-0004ke-R5 for pgsql-docs@postgresql.org; Thu, 27 Aug 2015 16:06:32 +0000 Received: from bruce by momjian.us with local (Exim 4.72) (envelope-from ) id 1ZUzh7-00036l-Iz; Thu, 27 Aug 2015 12:06:29 -0400 Date: Thu, 27 Aug 2015 12:06:29 -0400 From: Bruce Momjian To: "David G. Johnston" Cc: "pgsql-docs@postgresql.org" Subject: Re: Omission of "(or C)" in psql's "pset title" header Message-ID: <20150827160629.GK29674@momjian.us> References: <20150827020226.GG29674@momjian.us> <20150827151352.GJ29674@momjian.us> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) X-Pg-Spam-Score: -3.3 (---) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org On Thu, Aug 27, 2015 at 11:50:53AM -0400, David G. Johnston wrote: > Yes, I read that as "\pset tuples_only" and "\t" are alternate forms of the > same thing > and thought that "\pset title" and "\C" should be documented similarly. > Making "\pset C " work doesn't seem like an improvement. Well, making \pset C is at least consistent. We can't say "or C" without it. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. + -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs From david.g.johnston@gmail.com Sun May 24 04:56:28 2026 Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZUzr6-0008Bh-9E for pgsql-docs@arkaria.postgresql.org; Thu, 27 Aug 2015 16:16:48 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZUzr5-0000Df-OR for pgsql-docs@arkaria.postgresql.org; Thu, 27 Aug 2015 16:16:47 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZUzqk-0008GN-Sx for pgsql-docs@postgresql.org; Thu, 27 Aug 2015 16:16:26 +0000 Received: from mail-ig0-x231.google.com ([2607:f8b0:4001:c05::231]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1ZUzqi-0006WZ-4P for pgsql-docs@postgresql.org; Thu, 27 Aug 2015 16:16:26 +0000 Received: by igbjg10 with SMTP id jg10so20470790igb.0 for ; Thu, 27 Aug 2015 09:16:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=q7iA2PCRACy/SVVC0lKOo8OYWTDiQD/wisfkE6uj5ls=; b=t17bQYQE5VOsAEeCxzT9zX6ZSBE6RW1zUCRCxSO20A8rXbflVeMN1+uDL1FeoRJQCw HPOebUhg+PkN9Ok/uOYxEx//N1cGktBzUzuwyzkVgJQRMHcw1BITcoYy8BSKchgSSVfz Inc79yCYVai3e2galpbAPtqbIcnKOF0KsaUpH+NMyg8kzCQcvh/3I3KK6s2vXf1gKMa0 sDmkv1X6iJjpm8fJ6l0n+q5JYFWonHGtkrz2GnjyZOYdIoWSmvIGQBnrqGth764uTX74 pdON9zJ16VmjB1+1G4VNVBrpU6IfZAnkSwS5kH0tXqdKOx8fl/zAekS4SwQOf+Lb/8CZ MKUw== MIME-Version: 1.0 X-Received: by 10.50.129.5 with SMTP id ns5mr10645197igb.40.1440692182431; Thu, 27 Aug 2015 09:16:22 -0700 (PDT) Received: by 10.36.143.141 with HTTP; Thu, 27 Aug 2015 09:16:22 -0700 (PDT) In-Reply-To: <20150827160629.GK29674@momjian.us> References: <20150827020226.GG29674@momjian.us> <20150827151352.GJ29674@momjian.us> <20150827160629.GK29674@momjian.us> Date: Thu, 27 Aug 2015 12:16:22 -0400 Message-ID: Subject: Re: Omission of "(or C)" in psql's "pset title" header From: "David G. Johnston" To: Bruce Momjian Cc: "pgsql-docs@postgresql.org" Content-Type: multipart/alternative; boundary=047d7b3a9914c3bf3c051e4d49e0 X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org --047d7b3a9914c3bf3c051e4d49e0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thursday, August 27, 2015, Bruce Momjian wrote: > On Thu, Aug 27, 2015 at 11:50:53AM -0400, David G. Johnston wrote: > > =E2=80=8BYes, I read that as "\pset tuples_only" and "\t" are alternate= forms of > the > > same thing > > =E2=80=8B and thought that "\pset title" and "\C" should be documented > similarly. > > Making "\pset C " work doesn't seem like an improvement. > > Well, making \pset C is at least consistent. We can't say "or C" > without it. > > Agreed. --047d7b3a9914c3bf3c051e4d49e0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thursday, August 27, 2015, Bruce Momjian <bruce@momjian.us> wrote:

= On Thu, Aug 27, 2015 at 11:50:53AM -0400, David G. Johnston wrote:
> =E2=80=8BYes, I read that as "\pset tuples_only" and "\= t" are alternate forms of the
> same thing
> =E2=80=8B and thought that "\pset title" and "\C" = should be documented similarly.=C2=A0
> Making "\pset C <label>" work doesn't seem like an= improvement.

Well, making \pset C is at least consistent.=C2=A0 We can't say "o= r C"
without it.

Agreed.=C2=A0

--047d7b3a9914c3bf3c051e4d49e0-- From bruce@momjian.us Sun May 24 04:56:28 2026 Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1ZjGYt-0004CH-G1 for pgsql-docs@arkaria.postgresql.org; Tue, 06 Oct 2015 00:56:59 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84) (envelope-from ) id 1ZjGYt-0001EP-2Q for pgsql-docs@arkaria.postgresql.org; Tue, 06 Oct 2015 00:56:59 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84) (envelope-from ) id 1ZjGYs-0001Bm-47 for pgsql-docs@postgresql.org; Tue, 06 Oct 2015 00:56:58 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:256) (Exim 4.84) (envelope-from ) id 1ZjGYp-0006Mv-AL for pgsql-docs@postgresql.org; Tue, 06 Oct 2015 00:56:56 +0000 Received: from bruce by momjian.us with local (Exim 4.72) (envelope-from ) id 1ZjGYo-0000Mm-KS; Mon, 05 Oct 2015 20:56:54 -0400 Date: Mon, 5 Oct 2015 20:56:54 -0400 From: Bruce Momjian To: "David G. Johnston" Cc: "pgsql-docs@postgresql.org" Subject: Re: Omission of "(or C)" in psql's "pset title" header Message-ID: <20151006005654.GB9634@momjian.us> References: <20150827020226.GG29674@momjian.us> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20150827020226.GG29674@momjian.us> User-Agent: Mutt/1.5.20 (2009-06-14) X-Pg-Spam-Score: -1.9 (-) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org On Wed, Aug 26, 2015 at 10:02:26PM -0400, Bruce Momjian wrote: > On Wed, Jun 24, 2015 at 06:11:20PM -0400, David G. Johnston wrote: > > http://www.postgresql.org/docs/devel/static/app-psql.html > > > > The other pset keywords with black-slash aliases include a "(or )" > > paren after the keyword. �"title" does not (should be "C") > > Attached is a patch to implement this, including a doc patch. Patch applied. -- Bruce Momjian http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Roman grave inscription + -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs