From the Perltidy documentation section 'Controlling whether perltidy breaks before or after operators':

By default, perltidy breaks after these token types: % + - * / x != == + >= <= =~ !~ < > | & = **= += *= &= <<= &&= -= /= |= >>= ||= //= .= % += ^= x= And perltidy breaks before these token types by default: . << >> -> && + || //

The way I understand it is the -ci option lets you specify what happens to lines that are only broken because they are too long. Your example will break before the && not because of line length.(See corrections in the following nodes) From the documentation:

Code Indentation Control
-ci=n, --continuation-indentation=n
Continuation indentation is extra indentation spaces applied when a long line is broken. The default is n=2, illustrated here:

my $level = # -ci=2 ( $max_index_to_go >= 0 ) ? $levels_to_go[0] : $last_output_level;

I also found a line in the documentation that mentions a debug file. This also prints a .LOG file which gives details about the length of the lines and any warnings. "Also try the -D flag on a short snippet of code and look at the .DEBUG file to see the tokenization."


In reply to Re: Why is perltidy using indent-columns instead of continuation-indentation when breaking up a long if-line? by Lotus1
in thread Why is perltidy using indent-columns instead of continuation-indentation when breaking up a long if-line? by torgny

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":