Beefy Boxes and Bandwidth Generously Provided by pair Networks
Just another Perl shrine

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
I included the reasons behind my opinion in hopes of either hearing opposing reasons or pursuading those with opposing opinions.

I would have thought my reasoning to be self-evident, but perhaps that's a blind spot on my part. When deciding how to categorize (or recategorize) a post, I find that it helps to have a simple rule.

Is the post substantially about either the mechanisms or the overt policies of Perlmonks?
is the simplest, least ambiguous rule I could come up with. Perhaps it's too simple. But the more complex the rule set, the greater the likelihood of meta-argument. We don't have a category for meta-argument. :)

In reply to Re: Re^2: Are "PM Discussions" only to be technical? (reason) by dws
in thread Are "PM Discussions" only to be technical? by tye

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.