It doesn't have to be that big a deal. Make the change in one commit with no other code changes. If your existing style is consistent and PerlTidy is tuned well the number of changes will be fairly small in any case. If the number of changes is large that's a clue that your style across the code base is not consistent and may be a good driver for the switch to PerlTidy and enforced consistent style.

I've not used git, but I understand it offers very similar tools to Mercurial that would allow you to track changes to a line of interest using the file history. A "cosmetic" change set marked as such in its commit message is easy to ignore.

The big win for a team where style matters is that PerlTidy does an excellent job of formatting Perl and provides a great deal of control on exactly how style guides are provided.

I use PerlTidy extensively and haven't found a case yet where it has generated broken code from good code. It is likely to work well as part of a pre-commit processing hook for a revision control system to ensure committed code meets team style guides - and that may well be worth the pain of one slightly disruptive commit for a team that has a serious commitment to following their own style guidelines.

True laziness is hard work

In reply to Re^2: perltidy block indentation by GrandFather
in thread perltidy block indentation by saltbreez

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.