Perhaps a more interesting and agreeable idea is to allow each user to specify their own .perltidyrc and put it in their user config. Then, the server could
render everyone's <code> tags how
each user likes to see them.
Obviously, though, this still falls victim the habit that many monks have (myself included), of putting various code-like snippets in <code> blocks (like command-lines, shell scripts, psuedocode, code for other languages than perl). That could be dealt with with attributes: <code lang=perl>, or with a new tag like <perl> which behaves the same as <code> except for the auto-perltidy'ing.
Anyway, I suppose it's somewhat academic, because it probably ain't gonna happen, regardless, and I don't know that that's a bad thing.
------------
:Wq
Not an editor command: Wq
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.