From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: perltidy tweaks |
Date: | 2018-04-27 16:04:21 |
Message-ID: | b9dcadfd-0cb6-6a0b-d5d6-d9e06f31d9a6@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 4/26/18 14:10, Andrew Dunstan wrote:
>>> - Use option --nooutdent-long-quotes. This is similar to a change we
>>> made for pgindent in the C code a while ago. See patch for the results.
>> No strong opinion as to whether to do that or not, but if we do, I wonder
>> if we shouldn't also select --nooutdent-long-comments. I noticed a few
>> places where it was doing that (ie moving comments left if they went past
>> the right margin) and didn't particularly like it.
>
>
> Yeah, not a fan of the outdenting, so +1 to both of these.
committed all three
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Fabien COELHO | 2018-04-27 16:28:31 | Re: [HACKERS] pgbench - allow to store select results into variables |
Previous Message | Tom Lane | 2018-04-27 15:51:57 | Re: obsoleting plpython2u and defaulting plpythonu to plpython3u |