Voting inside longer sub-threads with many posts is easy, you select ++ or -- and hit return.

But the request will return at the very beginning of the page and you need to scroll again to were you started.

actually there are anchors allowing to return from where you voted, like

?node_id=11135115#11135141

one only needs to isolate the ID from the radio's name <input type="radio" name="vote__11135141" value="-1">

Minor complication is that one can vote on multiple nodes at the same time, identifying the one where the request was triggered might require some JS trickery.

update

In hindsight, implementing to vote with an AJAX request might be the better approach tho. It wouldn't require to reload the whole page and fiddling with the current vote mechanism.

Can someone with the proper access and authority please look into this? Thank you.

G'day All,

I had some problems with the rendering of the title of a post. I can't find any specific information: Super Search with keywords like title is not particularly useful. I suspect this may be documented somewhere; I hoping someone can point me to that.

The specific problem occurred with "Re^2: @ARGV ignores quotes [ZERO WIDTH SPACE]". That node's title currently renders as: Re^2: @ARGV ignores quotes [ZERO WIDTH SPACE].

Originally, the end of that was [&#8203;] which rendered as: Re^2: @ARGV ignores quotes [].

I didn't think that entity references were honoured in titles; however, this indicated I was wrong (or so I believed). I thought that would be an easy fix and changed the end part to [&amp;#8203;]; but that rendered as: Re^2: @ARGV ignores quotes [&amp;#8203;].

As I couldn't work out the apparently contradictory behaviour, I simply took a pragmatic approach and changed the end to [ZERO WIDTH SPACE] (its current value).

Any help with this would be appreciated.

How do I get "Newest Nodes" to permanently show more than the last 24 hours of questions again (i.e., get back to the way it was before I cleared "last checked time")?

Due to "popular demand", PerlMonks now supports Markdown formatting for writeups. Note: Initially, Markdown is only supported for comments (aka notes). If everyone likes it, we will extend the capability to root-level posts as well (SOPW posts, etc.)

Some relevant past discussions:

• Making Perl Monks a better place for newbies (and others)
• Wiki-Style syntax for posting
• better wiki-like shortcuts.
• Markdown syntax useful to the Monastery?

Sorry it took me a minute to implement this feature. :-D

To enable the use of Markdown in your comments, go to your User Settings and change the "Format writeups as:" selection from 'conventional' to 'markdown'.

Be aware that this is a global setting. You can't select the format at the time you submit the writeup.

When you are looking at a writeup entry box (textarea), you will see a short note immediately above it indicating which markup you can use.

This change was actually relatively simple to implement, since modules for converting markdown to HTML already existed.
I would like to know if there is any demand for any other Lightweight markup languages.
For example, we could add support for Textile or some flavor of wiki text.

This is a great idea for a "Grafana-ish" community dashboard collating metrics from various Perl sites and communities. Should PerlMonks offer to participate? (Sadly the author did not mention us in a list of resources he contemplates metering initially.)

I was looking for how to insert actual < and > on a comment and saw that under the comment box there is this (tags reducted):

• Snippets of code should be wrapped in ... tags not ... tags. In fact, ... 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 (... chars), in order to prevent horizontal scrolling (and possible editor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.

But the links either lead to nowhere (1st one) or lead to super-search with no results. Perhaps it can lead to a static page so as to reduce the burden to the site?

bw, bliako

Please open ?node_id=3989;BIT=www.google.com and click Search

I see

2021-05-07 and 2018-06-14 (searched 89.07% of DB).

90%? seriously?

I didn't get a notification for my reply here Re^3: Augmenting and reducing data structures (test)

I ran some tests with choroba++ and it seems that at least notifications for replies from one-self are unreliable/missing.

This is new, I haven't seen anything like this in the last 12 years...

Thursday April 4/22/2021

I'm not seeing any switch or option to turn on view all comments/replies in a thread, which is what I want so I can check a thread and see the entire thread, replies, comments, everything, at the same time. Is there such a view option? It's very difficult to actually read all replies and comments when you have to click many of them individually just to read what was hidden.

Also, I'd like to get rid of the "Replies are listed 'Best First'" sort because that's not the sort I want, I want either straight chronological, or nested chronological. This was particularly noticeable in a recent thread where 'best' had no meaning in the context of the thread, and the actual 'best' answers were actually hidden as comments you had to click to view.

ItÂ’s one

After I voted for the node, though, the encoding issue was gone:

It’s one 

I made screenshots of both the versions.

Update: I'm using Firefox 78.9.0esr on Linux.

I noticed the following error in nodelets about Montly/Weekly Best, maybe there is some work in progress?

Monthly Best
Internal problem occurred in get_picked_nodes
called with 10 bind variables when 9 are needed

Weekly Best
Internal problem occurred in get_picked_nodes
called with 10 bind variables when 9 are needed
[download]

L*