I didn't post the reply to your node after I noticed that you corrected yourself.

The more I look at this the more I can't figure out how you jumped to that conclusion after reading what I wrote. In particular, I said "then replied to my node based on a version from before your last update". If I had meant that you had posted after noticing my update, how would "[you] might want to check for updates [...] from others before replying" make sense? Or even "or, horror, wait a few minutes"?

What an odd thing to claim

Next time you think that, maybe you should delay replying to give your mind time to reflect and then re-read and see if your interpretation changes or your understanding improves.

but always before anyone replies

You can tell when some monk has started replying so that your silent updates don't make that monk's finished reply nonsense? Maybe you should consider having more patience before hitting "create" instead? Then there is just being polite to those who read your node before an update (and might be confused by a reply based on an update that they didn't notice, who might not want to reread your entire node doing a mental "diff" to figure out what you updated, or who didn't want to miss out on what you wrote since updates aren't (for good reasons) noted anywhere, etc.).

It'd be nice if "preview" showed the (up-to-date) node that you are replying to, such as below the input box (moving the relatively new "In thread" and "In reply to" headers down there as well). After I had composed my previous reply I checked for updates before actually posting (as I did with this reply, also checking that what I wrote actually makes sense with what was written). I'd rather throw away a composed reply than post a useless one. But it'd be cool if "preview" would make that a trivial task. Though this (or some other) distraction to delay me pushing "create" usually serves me well.

- tye        

In reply to Re^5: creating a variable in an if statement ("don't"s) by tye
in thread creating a variable in an if statement by Tanktalus

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.