Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl: the Markov chain saw
 
PerlMonks  

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??

I agree with the idea that reaping a node is serious stuff and that it should be done only in serious cases.

Editing a node though, especially when it requires only adding <code> or formating tags (gosh! why don't people just use the preview button and try to figure out why their post looks ugly?) is a much less serious matter. I still think that it should not be done without the node being considered and some edit votes cast on it (I usually wait for 3 edit and no keep). This is a simple measure to help preventing the power of editing to corrupt me: I only edit posts that other monks want to be edited, I don't decide it myself.

Changing the title of a node is a grey area. In most case a /msg to the author of the node, pointing out why a change in title would be nice, might be better than considering it.

Update: In any case, I think that the best way to get a post fixed is by messaging the author, as footpad did with this one actually ;--). Funny enough I did not remember Messaging authors of baddly formated posts by you which I posted a long time ago, but I guess I am consistent on this!

--
The Error Message is GOD - MJD


In reply to Re: On Responsible Considerations by mirod
in thread On Responsible Considerations by footpad

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.