Beefy Boxes and Bandwidth Generously Provided by pair Networks
No such thing as a small change

comment on

( [id://3333] : superdoc . print w/replies, xml ) Need Help??
I've noticed a few people link to nodes that aren't there but should be. (e.g. someone linked to MakeMaker when the only info is at perlman:ExtUtils::MakeMaker. Reaper got my attempt to link one to the other.) Maybe sometimes they link to a node that doesn't answer a question or provide as much info as certain other nodes.

I love this site, but searching is sometimes not as easy as I'd like, because the titles of nodes are not always the words that people would search with. Maybe it would be nice to see some crossnoding. Nodes that show up in searches and point to information already in the system. I think this would be useful. Nodes that point to one or more nodes. A place to put them. Could you put them in the discussions?

In reply to CrossNodes by Pedro Picasso

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.