I'm in this camp as well (well, I've got my own perldityrc that makes things like I liked them (which of course is contrary to the official settings at $work so I've gotta have two different copies so I can actually look at things sanely then broked them before checkin . . . :)). Very good point about the state of the code revealing state of mind; inconsistent indentation or ZOMGWTFBBQ complete lack thereof can point out stuff ("This entire block is outdented . . . maybe it's a pasteo").
That being said though, I can agree that it'd be a nice-to-have if there were (say) a "Download Tidy'd" link which would save me the trouble of cutting and pasting into a new document and then having the editor run-shell-perltidy over it manually. Less steps == less effort to look into problems == easier to help == more likely to bother actually replying.
Maybe some enterprising Greasemonkey guru could crank out something that would do something along these lines (not that'd do me any good since I primarily use Safari . . . ).
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
