Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
Maybe it's the idealistic side of me, but I personally believe we are 'Perl Monks', and not 'Perl Demons'. Maybe a discussion or two would be effected by a resolution to save original versions of a post, but for the most part I consider it futile. We should have the trust in our fellow monks. I percieve this as an attempt to form a contingency plan, and take up valuable hard drive space, for every squabble that arises. I think it would be best to leave perl monks the way it is, and not worry about these few cases. (unless the problem has become eminent in one too many cases, and contrary to my beliefs its not being blown out of proportion.)

Although if we are going to have this, I would definately concur with merlyn's sugestion.
Gyan Kapur

In reply to Re: New "feature" -- view nodes as they were originally posted by Revelation
in thread New "feature" -- view nodes as they were originally posted by blakem

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.