0095e11158
Revert to default of -pt=1 rather than -pt=2:
> -bt,-pt,-sbt: Container tightness
> These are parameters for controlling the amount of space within containing
> parentheses, braces, and square brackets. The example below shows the effect
> of the three possible values, 0, 1, and 2, for the case of parentheses:
>
> if ( ( my $len_tab = length( $tabstr ) ) > 0 ) { # -pt=0
> if ( ( my $len_tab = length($tabstr) ) > 0 ) { # -pt=1 (default)
> if ((my $len_tab = length($tabstr)) > 0) { # -pt=2
> A value of 0 causes all parens to be padded on the inside with a space, and
> a value of 2 causes this never to happen. With a value of 1, spaces will be
> introduced if the item within is more than a single token.
The tight parens decision was made in 2005 when .perltidyrc was introduced:
2535e77293
I tried pretty hard but couldn't find any previous discussion about this
decision, I'm not quite sure who supported it, who cared about it at all,
or who knew about it at all.
What I know is that I like pt=1 better. Nobody ever gets what they want
if they don't ask :)
16 lines
400 B
Plaintext
16 lines
400 B
Plaintext
|
|
-i=4 # 4 space indentation (we used to use 2; in the future we'll use 4)
|
|
-ci=2 # continuation indention
|
|
|
|
-sbt=2 # tight square parens
|
|
-bt=2 # tight curly braces
|
|
-bbt=0 # open code block curly braces
|
|
|
|
-lp # line up with parentheses
|
|
-cti=1 # align closing parens with opening parens ("closing token placement")
|
|
|
|
# -nolq # don't outdent long quotes (not sure if we should enable this)
|
|
|
|
|
|
|