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