Perltidy seems to think that this code: 
sub discover {
    return [ {
        'name' => $name,
        'version' => $VERSION,
    } ];
}

[download]
...would look better like this (I disagree): 
sub discover {
    return [ {
            'name' => $name,
            'version' => $VERSION,
        } ];
}

[download]
It's indenting the hash keys twice, presumably because there are two opening tokens. I'm using -sot "stack opening tokens".
But surely a large benefit of stacking opening parentheses and brackets is that you don't have to indent twice?
It's saving vertical space but wasting horizontal space.

Does anyone know the setting to control this? I've looked through the docs but not found it:
http://perltidy.sourceforge.net/perltidy.html#code_indentation_control

In reply to Perltidy indents too much when there are stacked opening tokens by will_

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.