News for hackers. Stuff that matters.
Re:StrictMark: Markdown, Refactored by legulere on Friday January 29, 2021 @03:16PM (#25961828)
lists are one of markdown's weak points though with numbered lists completely ignoring the numbers
Re:StrictMark: Markdown, Refactored by admax88q on Friday January 29, 2021 @03:27PM (#25961982)
Thats optimized for never having to renumber yoir lists as you edit your document.

I would hate to have to change 30 numbers because i want to move an item from last to first.

Re:StrictMark: Markdown, Refactored by hyperpape on Friday January 29, 2021 @04:35PM (#25962916)
Optimizing for readers definitely excludes lists like:

    2. 
    3. 
    5. 
    6. 
    1.
Re:StrictMark: Markdown, Refactored by setr on Saturday January 30, 2021 @11:22AM (#25970311)
Tbf it’d be trivial to have a button/flag to fix it in the source, and a warning to notify the user. It’d might be debatable to do so automatically, but on demand there’s no issue (like words table of content update/warning).

But the current definition of “its always sequential, that’s it” means you could do it automatically without changing meaning. Whereas do-as-I-say is stuck with being unsafe, always

Re:StrictMark: Markdown, Refactored by gerikson on Saturday January 30, 2021 @04:54AM (#25967767)
This is the same as HTML's <ol> though...