Re: Omission of "(or C)" in psql's "pset title" header

On Thu, Aug 27, 2015 at 11:13 AM, Bruce Momjian <bruce(at)momjian(dot)us> 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 <bruce(at)momjian(dot)us>
> 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
> <letter>)
> > "
> > > 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:
>
> <term><literal>tuples_only</literal> (or <literal>t</literal>)</term>
>
> 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.)
>
>
​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 <label>" work doesn't seem like an improvement.

David J.