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