Beefy Boxes and Bandwidth Generously Provided by pair Networks
"be consistent"


by ww (Archbishop)
on May 10, 2004 at 13:43 UTC ( #352046=user: print w/replies, xml ) Need Help??

How to RTFM

holli's Monk Links - Copy Perlmonks-links to the clipboard in on-site-format.


...and, re CB: "people generlly appreciate it if you take the extra 10 milliseconds to type all of the letters in your words instead of non-existent homophones particularly non-native speakers of English."

             belg4mit 2005-03-02 08:31:06-05

recent (or recently 'discovered') PM super_goodies:

...and Ovid's cgi tutorial (including charentitites Appx)

Why XP is NOT important:
19 Aug 05
You gained 2 experience points.
Your new level imbues you with super-powers! Check out Level 10: Saint for the details!
25 Jul 10
You gained 3 experience points.
Congratulations, you have been promoted to Canon!

Became 30th on Saints List, 5 Jan 2012 (29,397, 603 to go to Chancellor)

and, on 10 Feb 12 (ca 21:20 UT)
You gained 1 experience point. Do you want a medal, too?
Congratulations, you have been promoted to Chancellor!
You have 10000 points until level 22 - Bishop.

...and o/a 1 Dec 13, entered the 'top 20' on the Saints list.
    and at 0658 EST (US Eastern) on 1 Mar 14, ordained a "Bishop":
You gained 1 experience point.
Congratulations, you have been promoted to Bishop!
You have 10000 points until level 23 - Archbishop.

Posts by ww
TOC draft sample in Perl Monks Discussion
3 direct replies — Read more / Contribute
by ww
on Nov 07, 2017 at 08:14

    Draft, sample revision of Markup in the Monastery per LanX's excellent suggestion that we include TOC's in at least some informational nodes. Thanks LanX!
    Comments, please, from all (and see Re: TOCs and deeplinks for our house rules for background/my comments).

    Update/edit: per suggestions in replies from LanX and pryrt, some chapter titles in the body of the doc have been changed to more closely match the TOC entries.

    Markup in the Monastery


    Chapter 1 - Basics: Para & Code markup

    There are just two basic markup elements you MUST use when posting a comment or question:

    <p>...</p> Paragraph tags, so the narrative part of your node won't be an unreadable mismash.


    <c>...</c> Code tags around code and data (which can be cut and pasted direct from your editor).

    And now you know those, you can go back to creating your node unless you'd like to learn more.

    Chapter 2 Additional Markup (Overview+Examples)

    Here's a synopsis of important tags and their actions:

    Your PostPM Markup:Result:
    <p>first paragraph</p>
    <p>second paragraph</p>

    first paragraph

    second paragraph

    <p>The result is in <c>$array[0]</c></p>

    The result is in $array[0]

    use strict;
    use warnings;
    my @array = ("Hello world\n");
    if (@ARGV) {
        print $array[0];
    use strict; use warnings; my @array = ("Hello world\n";); if (@ARGV) { print $array[0]; } #
    Note: The "download" link is automatically displayed on <c>...</c> blocks. It links to a raw display of the displayed code. You don't need to do anything to enable this link.
    link to PM nodes by name
    Have you tried [Super Search]?
    Have you tried Super Search?
    Thanks for your help, [tye]
    Thanks for your help, tye
    Thanks for nothing, [tye|wiseguy]
    Thanks for nothing, wiseguy
    Link to PM nodes by ID
    Please consult [id://3989]
    Please consult Super Search
    External Links
    Did you try []?
    Did you try
    Other kinds of links
    (more info)
    Check out [pad://NodeReaper]
    Check out NodeReaper's scratchpad
    Did you check [doc://perlfaq]?
    Did you check perlfaq?
    text/font formatting
    This will be <b>bold</b>
    This will be bold
    This will be <i>italic</i>
    This will be italic
    This will be <tt>fixed width</tt>
    This will be fixed width
    Blockquotes (indented)
    A wise monk once said:
    "Indenting is good"
    .. and I agree
    A wise monk once said:
    "Indenting is good"
    .. and I agree
    My favorite flavors are:
    My favorite flavors are:
    • vanilla
    • chocolate
    How to make toast:
    <li>insert bread</li>
    <li>press button</li>
    How to make toast:
    1. insert bread
    2. press button

    Chapter 3 - Warnings & Tips

    PM markup code is NOT entirely w3c html 4.01 standard nor is it XHTML, so even if you're expert please scan these notes.

    Textual content:

    Ordinary paragraphing is accomplished with <p>...</p> tags, which (imprecisely) allow you to have your text appear in what may be called "conventional" paragraphs; that is with blank lines between paragraphs. That's highly recommended, as it makes your node easier to read.

    Links: Please, do NOT use <a href="">something</a>. Instead, create links (especially those to nodes at PM) using [...] The ... inside the square brackets may be a node's title or its id://(number). Optionally, you can override the target's title with your chosen alternate by adding |(some word or phrase) after the id or title before closing the square brackets.

    For example, [Super Search|Did you try to find that here?] will render as Did you try to find that here?. More extensive and sophisticated information can be found in What shortcuts can I use for linking to other information?.

    Lists: lists can be either ordered (decimal numbered - using Roman numerals or letters is beyond the scope of this note) or unordered (bulleted). One of each follows; first the ordered list, created with this:

    <ol><li>line 1 of list</li><li>line 2 of list</li><li>and so on</li><ol>

    1. line 1 of list
    2. line 2 of list
    3. and so on

    The unordered list uses <ul>...</ul> around the list item <li>...</li> tags:

    • line 1 of list
    • line 2 of list
    • and so on

    <b>...</b> can be used to enclose words, phrases or sentences you want to have appear in boldface. As a courtesy, do NOT abuse this... and use the preview function to check. Similarly, <i>...</i> can be used to italicize content.

    <tt>...</tt> tags surrounding a word or phrase (commonly, a single key word or symbol) cause that word or phrase to be rendered in something akin to a system font; eg: key words within the surrounding text.

    Heading tags, <h3>...</h3>, and smaller (through <h6>) may be used. Head tags, unsurprisingly, cause their content to render as headlines. For example

    <h4>A headline<h4>

    <h6>A smaller headline</h6>

    Any <hn> ... </hn> tag pair can be thought of as implying line breaks above and below (absent manipulation with css or other techniques far beyond the scope of this node). Please note that <h1> and <h2>are discouraged here.

    <blockquote>...<blockquote> is used to indent a (brief, please) segment of your text and works like this (the fixed width pseudo-tags, below, illustrate the actual useage):

    <blockquote>This is a blockquote. Note that it is indented both left and right and offset top and bottom by a blank line. This blockquote rambles on to ensure that regardless of the width of the viewer's browser window, there are multiple lines inside the blockquote. Note that there are no paragraph tags around this paragraph although using them would be allowed...and that it is permissible to include, for example, <b>textual</b> <i>markup
    </i><c> inside the blockquote. <p><c><p>
    What's more a blockquote can include multiple paragraphs. Again, this is padded with enough non-substantive verbiage to make it wrap in most user's browser windows.</p></blockquote>

    If you find it necessary (and you should make every effort to ensure it is NOT) to create a very long post, please use <readmore> ... </readmore tags. Should your post make it to the front page, the readmore segment collapses to a link by which the interested reader can see the entire post.

    Puzzle answers aka spoilers

    If you post a puzzle, enclose the answer in <spoiler></spoiler> tags, so you don't spoil the puzzle fun for others.

    Detail: <spoiler>...</spoiler> tags are intended to (temporarily) redact (in the intel world's sense; "black out") some brief piece of text or code whose visibility would spoil a thread for some future reader. Example:

    This sentence is inside spoiler tags.
    In a simple case, the material inside the spoiler tags will become visible when highlighted; the general idea being that a little more work is required to see the content than simply viewing a node.
    The reader's preference settings may cause <spoiler> tags to be rendered in unexpected ways.  Note that when wrapped in <c><code> tags the </c></c> tags will be treated as literal text.

    Nesting: Check for proper nesting. For example, if you open a paragraph tag, close it before beginning a blockquote or code segment. And that leads us directly to the next important pair of tags.


    Use code tags, <c>..</c> (or <code>...</code>), to post code and data. Doing so preserves your indentation, blank lines and those symbols for which use of character-entities is conventional elsewhere. Char-entities are discussed further, below

    A typical use would be to cut'n'paste your code into a PM node Code tags cause the code (or data) they enclose to appear in a distinguishable font. If you have turned on line-numbering in the section on "Code Listing Setings" in Display Settings the code lines will be numbered. The following is inside <c>...</c> tags.

    #!/usr/bin/perl use warnings; use strict; use (some module); if (some condition) { do something; and something more; # with a comment to make this a very, very lon +g line which will wrap in many browser windows, absent a gigundo moni +tor and so on. If you don't have auto code wrap on in "code," you'll +see a red plus sign and a lack of line number on the continuations af +ter wrapping is performed (sometimes at unfortunate points, as can be + seen in this instance, if you don't have auto code wrap turned on. } else { &whatever; # Note below } sub whatever { do something; }

    Note the download link, above. It appears after each stand-alone code block and allows readers to retrieve the code or data, without the line numbers.

    Note that in line 11 the "&" did NOT have to be written as a character entity (&amp;). If you're not seeing line numbering, see that setting in Display Settings.

    <pre> vs. <code>

    At first blush, the <pre> ...</pre> pair may look like an alternative to code tags... BUT DON'T USE IT HERE chiefly because <pre>...</pre> tags will not persuade the Monastery to provide a download link for the contents of the <pre>... and while it is now supposed to wrap lines that are too long for the viewer's browser window, there are ways Monks could use CSS that would defeat that. So, please. don't use <pre>...</pre> except to deal with exceptional cases... like that in the next paragraph (which still needs examples of using pre inside a long stretch of code).

    Exception: non-ASCII characters inside the ... may magically display as unrendered entities (i.e., as question-marks) instead of the character you expected, whereas inside <pre> ...</pre>, they may work as expected. (Thanks, pryrt).

    More untoward or problematic markup

    Inserting a <br> tag forces a newline at the point at which it's inserted. Monastery documents differ on its acceptability but in the form in this sentence, it generally works... while alternates, like XHTML's <br /> do NOT work.

    Using <div>...</div> tags is NOT deprecated, but unless you're expert in .html, you probably shouldn't use them here.

    <font (something="something")>... </font> tags are frowned upon. Don't use them except in extraordinary circumstances.

    Character Entities

    Please read carefully the hints which appear below the text entry box when you're creating a node. Outside code tags

    For: Use:
    &  &amp;
    <  &lt;
    >  &gt;
    [  &#91;
    ]  &#93;
    ®  &reg;
    ©  &copy;


    If you are a logged-in user, you have Display Settings which you can check or change. See particularly the section HTML Related Options. It is highly recommended that you check the checkbox and set the two other options to their maximum values (3 and 4, respectively). These will tell you quite clearly when you omit a required tag, and will help when you bork tag nesting rules.

    Most of the tags discussed above should be used in pairs (that is, <tag>... </tag>. While some of the other tags addressed in this node will DWIM even if you fail to close them, the <b>, <i>, and <tt> tags will not, nor will some "block level" tags like <ol>.

    A table listing all PM-approved html and arguments is available for those who wish to delve deeper.

    Beware of using your browser's "view page source" feature to see how a writeup has been formatted. Not only are you viewing a node after it has been processed by PerlMonks (turning What shortcuts can I use for linking to other information? into actual links, for example), but many browsers do additional processing on received pages, such as inserting missing closing tags.

    In the interest of brevity and simplicity, some statements above are oversimplified... and some do NOT apply to the CB, for which see PerlMonks Approved Chatter HTML Tags.

    ...and finally

    None of this will be much help if your content is unclear. Use an explanatory title, standard spelling, grammar, and punctuation. If posting a question, explain exactly what your problem is (and include warnings and error messages, verbatim, if received). Tell us what your input is in a separate code block or as a <DATA> section at the end of your code. Be explicit about the expected output, unless that's utterly unambiguous, and tell us how what you're getting, if anything, deviates from your expectations or desires.

    How do I post a question effectively?, Before You Post ... and On asking for help address many valuable points. If you're new to the Monastery, you'll profit greatly — EVEN IF YOU'RE IN A RUSH TO GET AN ANSWER — by reading these. And, oh yes, remember, "Your 'urgent need' is not our emergency."

    Back to the PerlMonks FAQ.

    As noted above, please comment here or address comments to ww.

perlnews item worth reading! in Meditations
No replies — Read more | Post response
by ww
on May 05, 2015 at 16:12
MJDs Contract Warnings - courtesy of Perlweekly in Meditations
4 direct replies — Read more / Contribute
by ww
on Mar 30, 2015 at 08:10
RFC: debugger_trainer in Meditations
4 direct replies — Read more / Contribute
by ww
on Dec 24, 2012 at 17:05

    Here's a first draft, incomplete implementation a possible response to my notion (YMMV) that Perl's CLI debugger is intimidating to novices (well, it was to me... for several years).

    IOW, here's a simple-minded, do-nothing, little script that invites the user to explore some debugger commands in circumstances in which s/he need not fear will be tantamount to rm rf (or del *.* /s, if 'doze in the learner's OS flavor).

    My hope is that the minimal set of operations in the script give a hint of (or maybe "are extensive enough for a start?") the range of debugger options/commands which the user would be well advised to learn.

    The specific RFC follows the code:

    #!/usr/bin/perl use 5.014; # modify to match your "perl -v" unless (@ARGV) { say "debugger practice; on restart, 1st arg must be a number\n"; exit; } say "Explore debugger commands w expr W expr b Ln|Event B Ln|Event (et +c incl l v s n)\n"; my ($var1, $var2, $var3); my @arr = qw (a b c d e f g); sub testable { # useless uninformative comment my $subvar1 = shift; say "\t In sub testable, \$var1: $var1"; my $subvar2 = shift; say "\t AS PASSED TO SUB, \$var2: $var2"; $subvar2 *= 5; say "\t In sub testable, \$subvar2: $subvar2"; my $subvar_rand_int = int(rand($subvar2)); say "\t In sub, \$subvar_rand_int is: $subvar_rand_int."; return $subvar_rand_int; # to $result } chomp($var1 = shift); $var2 = int(3*$var1); say "Pre_sub, \$var1: $var1 and \$var2: $var2"; push my @pass_to_sub,$var1; push @pass_to_sub,$var2; my $result = testable(@pass_to_sub); say "Back from sub with \$result: $result"; # another comment for exploration of the deugger for $_(@arr) { $_ .= "_foo"; say "$_ " x $result; say "\n"; }

    So, the question: are this notion and this approach worth pursuing, further, with additional scripts focusing on packages, OO, modules, etc... If so, where should that focus begin?

    Or should one, IYO, focus instead on getting noobs to use some of the available (often for $$$) GUI debuggers/other debuggers?

Preview for "Update" in Perl Monks Discussion
5 direct replies — Read more / Contribute
by ww
on Dec 05, 2012 at 17:40
    Brethern and Sistern (excuse the homo sap bias):

    For the too-many-th time, I discovered after posting that I'd omitted a critical point, markup or something else that left me dissatisfied with the node and then turned myself into a serial updater by adding an error for every correction.

    Therefore, seizing the bull by the bs ^H^H^H ... er, horns, may we discuss a possible change to the update capability; namely, an optional "preview before updating" configuration, which might be added to the option for direct posting without previewing which exists for Monks of certain orders?

    Alternately, we might add a second, "preview" button to the existing "update" button and redirect the action that way.

    And, actually I'm very curious about why this hasn't surfaced recently. It may be this has engendered little interest previously or that it's a fundamentally 'bad idea' or that it's in the 'too hard' box (but, without suggesting I'm sure I could do the job, I don't see why that would be the case).

    What say you?

RFC - shortform posting guidance for newcomers in Perl Monks Discussion
5 direct replies — Read more / Contribute
by ww
on Jan 04, 2012 at 12:12

    RFC. First Draft of proposed, shortform, guide to posting SOPW. Cuts, refs, negatives (but, yes, we all know that some people won't read guidance, no matter how brief) welcomed!

    5 Jan update: Reviewing Marto's suggestion, below, and the ++'s -- which in this case, I read as agreement -- how say ye to adding (as I've done below) li 7? Or do you lean to Eliya's view?   I've also replaced the "Ditto" in li 3. Also, reordered to keep code questions together.

    So, you're gonna' post a SOPW? Unneeded in last-second checklist. Stricken 5 Jan

    Here's a brief checklist for your question.
    1. Code tags ( <c> ... </c> ) tags around data and code?
    2. Includes a tiny snippet of (compilable) code that reproduces/illustrates your problem?
    3. Narrative description (not "doesn't work") of how that code falls short of your needs or expectations?
    4. Also provides sample data?
    5. Quoted, verbatim, all error messages and warnings (again, inside code tags!)?
    6. A title that identifies your topic (and no, that doesn't mean "Help, please" or a module name alone)?
    7. Post your OS, Perl (perl -v) and module (if relevant) versions?
    Here's some additional reference material:
    On asking for help   |   How do I post a question effectively?
    I know what I mean. Why don't you?   |   Markup in the Monastery

    ... and read the formatting tips around the the text-input and preview-edit boxes!

    See luis.roca's Re: RFC - shortform posting guidance for newcomers.
having same title while posting a new question in Perl Monks Discussion
1 direct reply — Read more / Contribute
by ww
on Dec 10, 2011 at 11:06
More re PM bug? in Perl Monks Discussion
2 direct replies — Read more / Contribute
by ww
on Nov 09, 2011 at 20:14

    More re PM Bug? ... because I can't reply to that thread... and after preview and create, I get what I've written and posted labeled as written by another monk (and same ID as the other monk's prior reply) -- but then that content never shows in the thread. Seems to have jetted off somewhere (but not the bit bucket?).

    Actually, same problem for me started with an attempt to reply to New site for perl... and I may have besmirched GrandFather's good reputation if my post ever actually shows up, since the rendered content after preview and create attributed comment to him:

    Thread: begins at New site for perl
    GrandFather's: Re: New site for perl
    (His actual post: questions failure to mention PM as a resource)
    Mine, when created after preview: same id, with this content:
    Tips'n Tricks->one liner: unix quoting with no qualifiers to stmnt that "This will print Hello oneliner in command line."
    Nope; it will print the Hello oneliner on the command line ONLY so long as the CLI is nix-=ish.

    Tutorial: "Introduction
    PERL - Practical Extraction and Reporting Language
    You do know that's a backronym, right?

    Tutorial (again): "File Handling" ...
    No example of 3 arg open?

    News: First item is announcement of the site by an individual wasting huge amounts of resources here?

    Update: Thanks to tye for the fix; 2nd blockquoted content above posted as intended now.</update>

    OTOH, you've done some neat stuff to render additional detail about examples, just for instance... So work on the content.

    Also noticed that BrowserUK has posted a node sometime today (lost its id; sorry) saying, loosely paraphrased, Ignore this; PM is all screwed up....

Thoughtless voting? in Perl Monks Discussion
12 direct replies — Read more / Contribute
by ww
on Jan 29, 2011 at 07:48

    Lately, I've been astounded when logging on as part of my morning routine. There, in the XP nodelet, is the news that I've "gained $n experience points."
    OK, so you might ask, "why 'astounded'?" Well, usually, I haven't written anything worth many upvotes.

    But what disturbs me is that it appears some nodes are getting multiple upvotes when they plainly 1 deserve to be downvoted. And to me, those upvotes suggest that those who cast them have succumbed to the temptations of XP-whoring or are voting without thoughtful evaluation of the content.

    Take this upvoted node2, for example, by a Monk with more than 500 posts and fewer than 50 XP3 (talk about someone with 'one year's experience, eight times)'

    Reputation: -9 (+3 -12)
    "Please could someone suggest modules or methods that would allow me to go into a bunch of Excel files and extract contents by sheet name. So there is a seperate output file for each class of sheet."

    Yep! No code; no sign of any effort, under-spec'ed, misspelling and all, and then, in response to the first reply (which points to Spreadsheet::ParseExcel), this:

    "Reputation: -6 (+2 -8)
    I am assuming that this is the better option of the two showing up, as of present. Does anyone have code that has done exactly what I wish to do. Please."

    So, "assuming" was worth two upvotes? I don't really think so, but we could debate that one, were it not directly followed by an explicit 'gimme!'

    However, moving on, lest I fail to offer evidence for frequent irresponsible upvotes, there's the notorious

    Reputation: -38 (+8 -46)
    perl -le 'print 5056.45 + 10112.92 == 15169.37 ? "as expected" : "perl math sucks!"'

    Trolling? "Dis-ing" Perl? Well, a charitable intpretation might be that this was really intended as a clever paraphrase of the accumulated wisdom on the imprecisions of floating point numbers... but in that case, it's surely not so unworthy as to draw so many - -s and thus is just the flip side of "unwarranted upvotes."

    And consider, please, another simple (if not explicitly articulated) 'gimme!'

    Reputation: -22 (+5 -27)
    I tried but I am too rusty. I need a program to : ....


    Reputation: -8 (+5 -13)
    Hi, i am using perl lite and having problem printing the soap response. The client is print a binary HASH value.
    how do i get the complete response (HTML) from the binary HASH value
    its SOAP lite

    So, to get to the point, do we perhaps need to rethink the awarding of XP for the act of voting?
    If so, some options, albeit flawed, might include:

    • Penalizing upvotes where some sufficient (ummm. Yeah, we might have trouble finding a concensus on a value for "sufficient") ratio of Monks have downvoted a node
    • Doing away with XP gains for voting
    • On weekends (when -- it seems to me -- the most egregious upvoting often occurs) suspending XP gains for voting
    • Granting XP gains for voting only at some minimum monk-ish level
    • Additional educational efforts -- perhaps utilizing a method something like the optional preview mode when posting a node or reply; also mandatory until some level of experience is attained
    • Creation of a (strictly limited) order of Monks -- call them "Editors" or "Censors" as you will -- charged with editing 'gimme' nodes (and whatever others are seen as particularly out of conformity with the values and customs of the Monastery) by prepending a warning -- something on the order of "Do NOT upvote this node. OP" ...(showed no effort | mistook the Monastery for a codewriting service | is grossly off-topic | etc)

    Is anyone else (concerned | annoyed | {some other negative}) about this? Or is this merely a worthwhile price for passing out votes on rep as we do?

    1 Well, YMMV, but the above are only a few example; not necessarily the most (IMO) grotesque.

    2 I've debated providing links to the nodes cited, and concluded that doing so would be tantamount to attacking the OPs ... and, in any case, if one wishes to verify my quotes and interpretation, Super Search will suffice.

    3 OK, that can be read as evidence that the system overwhelms the unwarranted upvotes -- in the most egregious cases. It's not so clear that's true of the majority of such upvotes -- ++s of nodes that are merely "so-so" or only "minimally bad."

    </rant> (for now....)

    Update(s): Re a few points raised below...and re possibly lack of clarity above.

    First and foremost, the rant is only tangentially about XP... and that, only in the sense that I have a suspicion that some votes are cast in hopes of obtaining XP.

    But it is very much about node rep and Anonymonk raises the question at Re: Thoughtless voting? very directly: "Does node reputation matter?"

    Since I can't answer the other two questions there, let me address the first... and my answer is a resounding "yes;" not for the writer's ego gratification but as a rough measure of the extent to which the node illuminates the topic at hand or provides pointers to relevant concepts; as a hint about the nodes perceived thoughtfulness; accuracy; wisdom; perceptiveness (or, sometimes, humor or even outstanding use of language). And if we were to develop a way to filter searches by rep, it could be a forward-looking guide, rather than merely retrospective (other than best nodes, PM discourages attempts to read node rep until AFTER the viewer has voted).

    On the other hand, I do hope the description of iguanodon's vote is tongue-in-cheek, or some of the irony mentioned elsewhere. Upvoting a node to see the tally skews the count and diminishes the value of that count for those who might later choose to up- or down- vote a node and then discover how well their view comports with whatever consensus, if any exists. (As I write this, about 3 hours after posting, the node's tally reflects no consensus).

    John Davies has an interesting point, too, re the voting pattern I discuss: "I don't see evidence that this is encouraging bad or discouraging good nodes."

    Nor do I; the Monastery has long had newcomers who bypass recommendations on how to frame a question... and a few, sadly, who've been here long enough to know better. But it's also a site where newcomers frequently raise questions or make comments that earn well-deserved reputations.

    But, John, I definitely see casting an upvote for a node where my assessment is '"OK, it's bad, but not that bad"' because as you say, that vote "may be incentive for some to upvote out of generosity...." From my (snarky) viewpoint, the appropriate generosity is in *not* downvoting the bad node (And anyway, there are too many *really good nodes* most days to waste votes and effort downvoting anything other than those which state something definitely untrue/inaccurate) or which really reflect a lack of interest in learning from good advice (in the vein of i didn't bother to study the docs you told me about; just gimme some code to do that job).

    This is becoming way too long, so just two more points:

    • ChuckularOne's parting observation seems suggest creating some 'measure of merit' accessible to visitors hoping for guidance on how any given Monk's guidance may stack up against some competing suggestion
    • ++ to wjw's comment. I don't buy all of it, but several points seem to be well worth thinking about.
Server glitches implicated in some dup posts? in Perl Monks Discussion
3 direct replies — Read more / Contribute
by ww
on Mar 09, 2010 at 13:11

    Lately (in ca 60 days < today -- 2010-03-09), I have been noticing an anomaly: my clicks on certain submit buttons (including "vote" in Newest Nodes, "preview" and "create" when creating a response to a parent node, and a few others (sorry, not logged as carefully as I should have) produce in response, rendering of the Gates (in the window of origin -- that is, where I clicked) instead of the expected outcome -- preview, create or vote cast..

    Anecdotal evidence in the CB and elsewhere, that others have also experienced this. In my case, it's occuring with w32 and linux vers of FFox, 3.5.n on both. My impression is that this "get the wrong page" phenomonon occurs most frequently -- but NOT exclusively -- when the site is exceptionally slow.

    A case in point is presently visible in this section; in my replies to id://827391.
    and, an instance I suspect, in cdarkes at id://827495 amd id://827494
    and -- who knows -- perhaps some of the items recently marked "please reap; inadvertent dup" (or words to that effect) from posters who are among the most senior of Monks.

    Full Disclosure: Though I am honored by inclusion among devils, I'm not sufficiently skilled to track down a suspected cause and propose a solution.

Log In?

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

How do I use this? | Other CB clients
Other Users?
Others taking refuge in the Monastery: (7)
As of 2019-06-18 10:41 GMT
Find Nodes?
    Voting Booth?
    Is there a future for codeless software?

    Results (81 votes). Check out past polls.

    • (Sep 10, 2018 at 22:53 UTC) Welcome new users!