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??
OK. I hate to make YAFR (yet another feature request), but today I was reading Using # inside qw() and I thought to myself, "good question, has code, but the title could be better to help others find this when searching." I know I could make a request to the powers that be to change the title for that purpose, but it struck me that I'd rather be able to let the author know what I thought and why and see if s/he wanted to do that. Basically, I wished I could make a reply that was of an editorial nature. I could message the monk, or I could just make a normal reply. But it feels like I'd be cluttering an otherwise good pure perl strain with silly site related matters.

This node comes as a question. I want to know if anyone else finds themselves wanting to do this and also not doing it because it would just be noise in some senses. I want to also make it clear that this is NO slight on Chady - if anything I only had my thought because it was a good, well formed, on topic question that I think should be easily accessed through searches by other seeking wisdom. What do you think? Should there be a way to make replies that maybe only appear to the author? Should thre be two threads for every node? Am I just too bored today? =)

We speak the way we breathe. --Fugazi


In reply to making editorial replies? by jptxs

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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others lurking in the Monastery: (8)
As of 2024-03-28 17:07 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found