From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Smith <smithpb2250@gmail.com>
cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Subject: Re: pg_createsubscriber TAP test wrapping makes command options hard to read.
In-reply-to: <CAHut+Ps6Q+i_3xS6H7ybw3-hx9+2QOuneTJwHArxqxFnKX5+4g@mail.gmail.com>
References: <CAHut+PvfaUZQR3rEnj-Dcg_6713Wu4yRdd-yZkkC9NVsARht8A@mail.gmail.com> <556792.1733967676@sss.pgh.pa.us> <CAHut+Ps6Q+i_3xS6H7ybw3-hx9+2QOuneTJwHArxqxFnKX5+4g@mail.gmail.com>
Comments: In-reply-to Peter Smith <smithpb2250@gmail.com>
	message dated "Thu, 12 Dec 2024 13:32:19 +1100"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <564914.1733971586.1@sss.pgh.pa.us>
Date: Wed, 11 Dec 2024 21:46:26 -0500
Message-ID: <564915.1733971586@sss.pgh.pa.us>
Archived-At: <https://www.postgresql.org/message-id/564915.1733971586%40sss.pgh.pa.us>
Precedence: bulk

Peter Smith <smithpb2250@gmail.com> writes:
> The strange thing is there are other commands in that file very
> similar to the ones I had changed but those already looked good, yet
> they remained unaffected by the pgperltidy. Why?

You sure it's not just luck-of-the-draw?  I think that perltidy
is just splitting the lines based on length, so sometimes related
options would be kept together and sometimes not.

			regards, tom lane