Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hSPax-0003T8-Uo for pgsql-hackers@arkaria.postgresql.org; Sun, 19 May 2019 17:27:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hSPaw-0005yh-MA for pgsql-hackers@arkaria.postgresql.org; Sun, 19 May 2019 17:27:34 +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_SHA1:256) (Exim 4.89) (envelope-from ) id 1hSPaw-0005ya-Dg for pgsql-hackers@lists.postgresql.org; Sun, 19 May 2019 17:27:34 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hSPau-0005LN-1Q for pgsql-hackers@postgresql.org; Sun, 19 May 2019 17:27:34 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id x4JHRLct032166; Sun, 19 May 2019 13:27:21 -0400 From: Tom Lane To: Piotr Stefaniak cc: Thomas Munro , Pg Hackers , Michael Paquier Subject: Re: Emacs vs pg_indent's weird indentation for function declarations In-reply-to: References: <7659.1548653310@sss.pgh.pa.us> <20190128070842.GF15401@paquier.xyz> <14259.1557895390@sss.pgh.pa.us> <9170.1557955021@sss.pgh.pa.us> <17265.1557955842@sss.pgh.pa.us> <16886.1558104483@sss.pgh.pa.us> Comments: In-reply-to Piotr Stefaniak message dated "Sun, 19 May 2019 17:25:05 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <32164.1558286841.1@sss.pgh.pa.us> Date: Sun, 19 May 2019 13:27:21 -0400 Message-ID: <32165.1558286841@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Piotr Stefaniak writes: > On 17/05/2019 16.48, Tom Lane wrote: >> It doesn't really seem practical to me to make the lookahead function >> smart enough to tell the difference between attributes and K&R-style >> parameter declarations. What I'm thinking of doing to have an >> upstreamable patch is to invent a new switch, perhaps '-kr'/'-nkr', >> to indicate whether the user is more worried about K&R function >> declarations than she is about function attributes. > I think it's safe to assume that upstream can drop support for K&R-style > parameters altogether. Cool. I already created the switch, but maybe we could have it default to -nkr? regards, tom lane