Re: pgindent - Mailing list pgsql-hackers

From Robert Haas
Subject Re: pgindent
Date
Msg-id CA+TgmoYaQJ42qwurx2X_gwU-uBFBNv9mAdG1Gk12TDw0ikD_8Q@mail.gmail.com
Whole thread Raw
In response to Re: pgindent  (Andres Freund <andres@anarazel.de>)
Responses Re: pgindent  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On Wed, Apr 27, 2016 at 11:45 AM, Andres Freund <andres@anarazel.de> wrote:
> Yes, that makes sense. That way other can easily look at "their" code,
> to see whether it can be made more pgindent resistant ;)

Right.

>> It mostly just adds new typedefs that have
>> appeared over the last year, but it also realphabetizes the file -
>> some things that were added incrementally seem to have ended up in
>> what is, at least according to what sort likes to do on my machine,
>> the wrong place in the file.
>
> Is it just me, or is the sort order in that file a bit confusing? The
> whole thing about upper and lower case being separated seems to make it
> much harder than necessary to manually insert something in the right
> place..

Except for recently-manually-added entries, it seems to match what
sort wants to do on my system exactly.  Which seems good.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Suspicious behaviour on applying XLOG_HEAP2_VISIBLE.
Next
From: Robert Haas
Date:
Subject: Re: pgindent