postgresql/src/tools/pgindent/perltidyrc

--add-whitespace
--backup-and-modify-in-place
--backup-file-extension=/
--delete-old-whitespace
--entab-leading-whitespace=4
--keep-old-blank-lines=2
--maximum-line-length=78
--nooutdent-long-comments
--nooutdent-long-quotes
--nospace-for-semicolon
--opening-brace-on-new-line
--output-line-ending=unix
--paren-tightness=2
--paren-vertical-tightness=2
--paren-vertical-tightness-closing=2
--noblanks-before-comments
--valign-exclusion-list=", = => =~ |= || && if or qw unless"
Remove whitespace from end of lines 2013-05-31 03:05:07 +02:00			`--add-whitespace`
			`--backup-and-modify-in-place`
perltidy: Don't write backup files Newer perltidy versions can just avoid writing backup files, so we don't need the old dance of deleting them afterwards. Supported since 20120619. https://metacpan.org/source/SHANCOCK/Perl-Tidy-20120619/CHANGES#L61 2018-03-21 15:09:37 +01:00			`--backup-file-extension=/`
Remove 'for' loop perltidy argument, and move args to perltidyrc file. Backpatch to 9.2. Per suggestion from Noah Misch 2012-06-16 16:12:50 +02:00			`--delete-old-whitespace`
Remove whitespace from end of lines 2013-05-31 03:05:07 +02:00			`--entab-leading-whitespace=4`
			`--keep-old-blank-lines=2`
Remove 'for' loop perltidy argument, and move args to perltidyrc file. Backpatch to 9.2. Per suggestion from Noah Misch 2012-06-16 16:12:50 +02:00			`--maximum-line-length=78`
perltidy: Add option --nooutdent-long-comments 2018-04-26 20:13:46 +02:00			`--nooutdent-long-comments`
perltidy: Add option --nooutdent-long-quotes 2018-04-26 17:52:52 +02:00			`--nooutdent-long-quotes`
Remove whitespace from end of lines 2013-05-31 03:05:07 +02:00			`--nospace-for-semicolon`
Remove 'for' loop perltidy argument, and move args to perltidyrc file. Backpatch to 9.2. Per suggestion from Noah Misch 2012-06-16 16:12:50 +02:00			`--opening-brace-on-new-line`
			`--output-line-ending=unix`
Remove whitespace from end of lines 2013-05-31 03:05:07 +02:00			`--paren-tightness=2`
Restrict vertical tightness to parentheses in Perl code The vertical tightness settings collapse vertical whitespace between opening and closing brackets (parentheses, square brakets and braces). This can make data structures in particular harder to read, and is not very consistent with our style in non-Perl code. This patch restricts that setting to parentheses only, and reformats all the perl code accordingly. Not applying this to parentheses has some unfortunate effects, so the consensus is to keep the setting for parentheses and not for the others. The diff for this patch does highlight some places where structures should have trailing commas. They can be added manually, as there is no automatic tool to do so. Discussion: https://postgr.es/m/a2f2b87c-56be-c070-bfc0-36288b4b41c1@2ndQuadrant.com 2018-05-09 16:14:46 +02:00			`--paren-vertical-tightness=2`
			`--paren-vertical-tightness-closing=2`
Don't force a blank line before comments in perl code Suggestion from Bruce Momjian Discussion: https://postgr.es/m/20180525190445.GA2213@momjian.us 2018-05-27 14:53:54 +02:00			`--noblanks-before-comments`
Make agreed-on updates in perltidy options. Our standard version of perltidy is now 20230309. Add a --valign-exclusion-list setting to reduce crosstalk between nearby lines of Perl code. Also, update instructions for running pgindent (missed in b16259b3c). Discussion: https://postgr.es/m/20230428092545.qfb3y5wcu4cm75ur@alvherre.pgsql 2023-05-19 22:43:57 +02:00			`--valign-exclusion-list=", = => =~ \|= \|\| && if or qw unless"`