No that's to do with how I usually run perltidy as a filter from emacs and want it to simply print out the tidy'd contents rather than rewrite based on the the input file directly. From the docs: 

    -st, --standard-output
        Perltidy must be able to operate on an arbitrarily large number of
        files in a single run, with each output being directed to a
        different output file. Obviously this would conflict with outputting
        to the single standard output device, so a special flag, -st, is
        required to request outputting to the standard output. For example,

          perltidy somefile.pl -st >somefile.new.pl

        This option may only be used if there is just a single input file.
        The default is -nst or --nostandard-output.

    -se, --standard-error-output
        If perltidy detects an error when processing file somefile.pl, its
        default behavior is to write error messages to file somefile.pl.ERR.
        Use -se to cause all error messages to be sent to the standard error
        output stream instead. This directive may be negated with -nse.
        Thus, you may place -se in a .perltidyrc and override it when
        desired with -nse on the command line.

The cake is a lie.
The cake is a lie.
The cake is a lie.

In reply to Re^5: Code style question by Fletch
in thread Code style question by AlexP

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


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.