Re: perltidy tweaks

From: Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: perltidy tweaks
Date: 2018-04-26 18:10:31
Message-ID: f9684b68-f685-8ac0-0969-2ee40c8538fe@2ndQuadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 04/26/2018 12:33 PM, Tom Lane wrote:
> Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
>> I prpose two tweaks for the perltidy configuration:
>> - The new perltidy version can avoid writing backup files, so we don't
>> need to explicitly delete them after.
> +1

+1

>
>> - 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.

>
> What would be more per project style is to reflow overly-wide comments
> into multiple lines, but I don't see an option for that :-(
>
>

Right. Maybe we need a script that at least identifies them for us.

cheers

andrew

--
Andrew Dunstan https://www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2018-04-26 18:48:52 Re: Toast issues with OldestXmin going backwards
Previous Message Robert Haas 2018-04-26 17:39:47 Re: [HACKERS] Clock with Adaptive Replacement