Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
Dunno about generally accepted, but I do something like this:
  • If I just correct a simple spalling misstake in normal text, I don't bother pointing that out (unless it was pointed out to me, and an official thank you is appropriate).
  • If I clarify my point, adds whole sentences or change the "spirit" of the post etc, I generally do that in an Update: block, or point it out from a such.
  • Changes to code I almost always point out, the exception being if I catch it immideately after hitting submit, I may just correct it fast, trusting the odds that noone had the time to copy or download it yet.

Some people tend to write whole changelogs, some even timestamped for every change they make, including typo edits and other stuff. While I am too lazy to do that myself, I kinda like reading those. It shows that the post is alive and maintained by the owner. Oftenly I guess it is overkill, but if one has the stamina to do such, keep it up. :)

I think pointing out edits is mostly only necessary if it would mean something to anyone reading it both before and after the edit in question. But it is also a nice tool to show how you were thinking from the start, and how that thinking might have changed - it is a part of how you write, in a way.


You have moved into a dark place.
It is pitch black. You are likely to be eaten by a grue.

In reply to Re: Post-Posting Etiquette by Dog and Pony
in thread Post-Posting Etiquette by tadman

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 surveying the Monastery: (3)
As of 2024-04-19 17:03 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found