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":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.