this post was submitted on 04 Jun 2025
336 points (97.7% liked)

Programmer Humor

23795 readers
2636 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] squaresinger@lemmy.world 4 points 1 day ago (1 children)

It's not the client, it's markup.

[–] WhyJiffie@sh.itjust.works 2 points 1 day ago (1 children)

this is not a defined thing in markdown, just the markdown renderers of some clients do it

[–] squaresinger@lemmy.world 1 points 1 day ago (1 children)

This here is apparently the original source of the markdown specification, and there it clearly says that this is the correct behaviour: https://daringfireball.net/projects/markdown/syntax#list

Ordered lists use numbers followed by periods:

  1. Bird
  2. McHale
  3. Parish

It’s important to note that the actual numbers you use to mark the list have no effect on the HTML output Markdown produces. The > HTML Markdown produces from the above list is:

If you instead wrote the list in Markdown like this:

  1. Bird
  2. McHale
  3. Parish

or even:

  1. Bird
  2. McHale
  3. Parish

you’d get the exact same HTML output

[–] WhyJiffie@sh.itjust.works 1 points 21 hours ago (1 children)

hmm, you are right. it's not actually a bug in the renderer then

[–] squaresinger@lemmy.world 1 points 21 hours ago* (last edited 21 hours ago)

The only difference to the standard that I see is that the standard says it should be 1,2,3,4,5, while at least for me it renders as 5,6,7,8,9.

But that's probably because it doesn't render as HTML and thus doesn't rely on HTML to do the numbering.