That's a good point. However, if we1 can put in heuristics to the PM code to decide when code tags are required (and are not actually present), and we decide these heuristics are accurate (i.e., zero false-positives, few false-negatives), and we decide that this would be beneficial to the community at large, then we could make it mandatory: no "submit" button until all warnings are dealt with.
I would propose that there also be a way around these heuristics. That is, I like the computer being smart. But not too smart. For example, perhaps if you submit a preview without having changed anything, then you get the submit button on the next preview. Or, perhaps, there is a checkbox saying, "ignore warnings" which, if unset (default) would make the submit button act as the preview button.
And then, any time warnings are bypassed, perhaps we could automatically consider the node for those warnings? :-)
1 I'm using a very, very loose definition of "we" here. As in, "we" == "gods".
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||