summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDylan William Hardison <dylan@hardison.net>2017-07-14 18:55:15 +0200
committerGitHub <noreply@github.com>2017-07-14 18:55:15 +0200
commit73707dc43ec352cddb6c8ca9463c80cb00e9eae6 (patch)
tree6400deb65ddf6763a2429247cb8089828e0b311c
parent6cf2172e2c3f442dca8d8755622d7e598a45899f (diff)
downloadbugzilla-73707dc43ec352cddb6c8ca9463c80cb00e9eae6.tar.gz
bugzilla-73707dc43ec352cddb6c8ca9463c80cb00e9eae6.tar.xz
replace perltidyrc with on that specifies -pbp with two exceptions
previously, the perltidyrc was written with the original recommendations of the upstream bugzilla project. The style used there is... inconsistent at best. For a while now, I've been using perltidy -pbp and telling others to do the same for new code. However there are two exceptions to -pbp that are widely useful: 1. line length can be up to 120. 2. brace vertical tigntness is turned off. This means that there is always a newline after the { in a multi-line brace construct.
-rw-r--r--.perltidyrc19
1 files changed, 3 insertions, 16 deletions
diff --git a/.perltidyrc b/.perltidyrc
index 288712461..25f9ef626 100644
--- a/.perltidyrc
+++ b/.perltidyrc
@@ -1,16 +1,3 @@
---block-brace-tightness=0
---brace-tightness=1
---continuation-indentation=2
---indent-columns=4
---line-up-parentheses
---maximum-line-length=120
---noblanks-before-blocks
---opening-brace-always-on-right
---opening-token-right
---paren-tightness=2
---square-bracket-tightness=2
---stack-closing-tokens
---stack-opening-tokens
---vertical-tightness-closing=2
---vertical-tightness=2
---want-break-after="."
+--perl-best-practices
+--brace-vertical-tightness=0 # always break after {
+--maximum-line-length=120 # max line length is 120