Re: Omission of "(or C)" in psql's "pset title" header
От | Bruce Momjian |
---|---|
Тема | Re: Omission of "(or C)" in psql's "pset title" header |
Дата | |
Msg-id | 20150827151352.GJ29674@momjian.us обсуждение исходный текст |
Ответ на | Re: Omission of "(or C)" in psql's "pset title" header ("David G. Johnston" <david.g.johnston@gmail.com>) |
Ответы |
Re: Omission of "(or C)" in psql's "pset title" header
|
Список | pgsql-docs |
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@momjian.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.) -- Bruce Momjian <bruce@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + Everyone has their own god. +
В списке pgsql-docs по дате отправления: