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 1hR1UF-0004mT-ER for pgsql-hackers@arkaria.postgresql.org; Wed, 15 May 2019 21:30:55 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hR1UE-000177-9d for pgsql-hackers@arkaria.postgresql.org; Wed, 15 May 2019 21:30:54 +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 1hR1UE-000170-1F for pgsql-hackers@lists.postgresql.org; Wed, 15 May 2019 21:30:54 +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 1hR1UC-00038J-Lz for pgsql-hackers@postgresql.org; Wed, 15 May 2019 21:30:53 +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 x4FLUgcq017266; Wed, 15 May 2019 17:30:42 -0400 From: Tom Lane To: Thomas Munro cc: Pg Hackers , Michael Paquier , Piotr Stefaniak 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> Comments: In-reply-to Thomas Munro message dated "Thu, 16 May 2019 09:26:47 +1200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <17264.1557955842.1@sss.pgh.pa.us> Date: Wed, 15 May 2019 17:30:42 -0400 Message-ID: <17265.1557955842@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Thomas Munro writes: > On Thu, May 16, 2019 at 9:17 AM Tom Lane wrote: >> A small problem with the "rejiggering" is that it now makes the wrong >> choice for K&R-style function definitions, causing them to be weirdly >> indented. For our purposes, that's a non-problem so I'm not excited >> about trying to make it smart enough to recognize those. We do have >> a couple of amazingly old and crufty K&R-style functions in src/port/, >> though, so probably we'd wish to fix those. > What kid of fork is pg_bsd_indent... do we care about upstreaming > changes? I guess someone would need to deal with that case eventually > if so. We regard the FreeBSD copy as upstream, and I think we're mostly in sync with that but only mostly. So it would come down to whether the FreeBSD maintainer is worried about K&R mode and what he wants to do about that. Piotr, that's still you isn't it? regards, tom lane