Just a thought. But I wondered how it might be received to have announcements in the nodelets area,. That scrolled up, much like the CB does. But with announcements of the PerlMonks users that have just graduated to a higher level. It seems fitting of the theme, and times; hoisting a tankard to a fellow Monk who has just graduated to a higher level. I dunno. Just a thought. I thought it might attract people, or possibly be well received.
use Perl::Always or die;
my $perl_version = (5.12.5);
I think I'm missing something: I can't seem to link into the middle of a document on CPAN as I would expect to be able to do. So I expect that either: (a) Someone may need to tap me with a cluebat, or (b) we may be missing a documentation shortcut.
Context: While answering a question (Re: Is it possible to run SQL select in Oracle ... tl;dr), I wanted to link to the fetchrow_hashref function in the DBI docs in CPAN. I expected that we would have a shortcut that could do so, but I wasn't able to figure out how to do it nicely.
For more than three hours yesterday, the Perlmonks website was broken: it was impossible to post any new writeup. It was me who caused this downtime by urging Corion to apply a particular pmdev patch I wrote, when that patch had a bug. I hereby apologize to all monks.
The details. The downtime lasted between approximately 2013-11-15 15:00 UTC to 2013-11-15 18:45 UTC. The patch was looksLikeSpam - (patch).
A few nights ago, I went looking to find other options in the way of editors to try out. I found links to Code Editors and Development Environments and Perl Development Tools, and began opening links to see what each was about. I found several links, however, that appear to have suffered bit-rot, and thought I should bring it to someone's attention. Where I could, I have tried also to find or suggest updated or possibly better links.
A slightly different problem than my previous post .. creating a post with the spoiler tags already in place means that, after a preview, the spoiler is .. hidden. And if I click on the link to reveal the spoilers, my post disappears (yay for the Back button).
No problem, I ended up replacing the spoiler tags with text like spoiler here soon, and made sure to put the spoiler tags back in once I as done editing.
Just now I tried to respond to one of Tanktalus's posts that contained a spoiler. Since I wanted to respond specifically to the material in the spoiler, I revealed the spoiler (shown here), then clicked on reply -- only to get the node with the spoiler hidden again.
I can work around this, but .. I think that's a bug. :)
I've poured pored over all the Friar duties and responsibilities links (perhaps too many at once is my problem) and I find a conflict.
On one hand it says we don't correct spelling; on the other hand it says the titles are the key to long term usability of the site.
So what happens when a keyword for search is misspelled in the title?
I recently submitted what I think was my first NTC and I may have committed a social faux pas, in that I requested a spelling correction on node title.
Just looking to see if I should refrain from that particular activity in the future, given my confusion after reading conflicting guidance in the veritable sea of PerlMonks documentation. :-)
Update: Thanks to everyone who sent me private chat messages with s/poured/pored/. I was starting to think it was some kind of old PerlMonks insider joke or something, but after getting multiple identical messages, it finally dawned on me that I might have a typo in my post.
General:I have just recently started actively indulging in my civic responsibility by going to the "Nodes for consideration" and tossing in my two cents worth.
I thought it might be useful to be able to sort the section entries by those that I have already votes on as compared to those I have not, putting those that I have not at the top so that they are readily available, and those that I have towards the bottom.
Proposal:Sort of the work to do first, and the work done last.
(I did do a super search to see if this had been suggested before, but did not find this issue addressed as far back as 2004.)
My thinking is that (assuming the results come from a DB) this would be a simple addition of an "order by" in the query.
(I did also look around for an existing way to "personalize" the display of this section, no luck. So if I missed it, please let me know.)
Gives the advantage of getting to the work to do first, without wading through the work that has been done already
Thanks for taking the time to read this, and do educate me if this seems foolish.
Suggestions by others:
A good idea added by Athanasius below - Add "submit" to top of page - ...Thanks!
kcott pointed out that it was unclear whether or not I was asking for considerations to be broken out into their originating sections. For clarification: I am not interested in that. Only that the things to be done come prior to the things that have already been done. Thanks kcott for pointing that out!
ambrus asked that the title be change to correctly identify the subject(Also added to the text of the node). Thanks ambrus! Done.
Update:(second update to clean up a damned closing tag)
So, It has been a while and I think anyone who was interested commented. Thanks much for that. In the mean time, I have learned a bit due to some of those comments and because I spent more time on the site. I can see that the suggestion has limited value relative to other issues at the site. On the other hand, like I said, I certainly learned along the way.
I appreciate the feedback and the patience of those that have been about the place for a while and am satisfied.
'nough said on this subject! :-)
Next pint of ale is on me...
...the majority is always wrong, and always the last to know about it...
..by my will, and by will alone.. I set my mind in motion
is there a section here where I could post a script and have interested/bored people help me improve it? It's working as intended but I would like to escape the "self-taught-nastyness" and improve my overall understanding and scripting style.
It is lengthy (alltogether ~1k relevant lines) which is why I didn't post it right away.
Apologies if this is the entirely wrong place for something like that.