Petition to move to Discourse CI
-
Is a temporal bugfix one that only ever existed in one timeline, one that @codinghorror has no memory of?
-
Is a temporal bugfix one that only ever existed in one timeline, one that @codinghorror has no memory of?
Schrödinger's bug?
-
One of your devs (EvilTrout?) fixed it very shortly after the new Markdown spec whatever-its-called made that the correct behavior.
Really? Can you point to the public GitHub checkin where this happened?
I bet you can't. Because that never happened, and there is as of yet no final CommonMark spec.
(For the record I do support it as a logical numbered list behavior change, but we have to control the Markdown spec to make these changes in a meaningful way for the world.)
-
Really? Can you point to the public GitHub checkin where this happened?
Oh well if you're that determined to defend that your product's been buggy forever, then I'll concede the point.
You're product is a piece of shit and has been forever. Go drown yourself.
(For the record I do support it as a logical numbered list behavior change, but we have to control the Markdown spec to make these changes in a meaningful way for the world.)
Yeah; MAKING THE THINGS PEOPLE TYPE ACTUALLY APPEAR ON THE SCREEN is a pretty low-priority thing for a forum.
-
It was fixed at one point. As a joke I started doing ordered-lists using non-nonsensical number sequences and letting the software fix it for me, and I was surprised when it started actually using the numbers I entered.
I don't recall when it was, but it didn't last long.
-
I tried fixing that code once, perhaps in the old parser, but in the current one its probably around the absolutely hairiest part of the code. I seriously estimate it will take me about a week to implement it.
Why not raise an issue here https://github.com/evilstreak/markdown-js ?
Why not try at it yourselves, many very strong JS devs around here. I just can not afford to spend a week on this at the moment unless some customer funds it.
-
The rest is code formatted. Or should be.)
Nope, indented list!
-
one space
2. five spaces
1. nine spaces
1. thirteen spaces -
one space
2. five spaces
1. nine spaces
1. thirteen spacesblank line, then seventeen spaces the blank line makes the list items be wrapped in <p>s
-
-
Shakespeare was a monkey as much as we are as well ... so I am not sure what your meaning is.
-
I seriously estimate it will take me about a week to implement it.
Seriously?
And that's the new parser - the one you guys presumably rewrote to fix issues with the old parser?
I'm not going to blakeyrat here, but damn.
-
We did not write that parser, it was the most extensible one around last year and we do a ton of extensions to markdown, unfortunately the internals are ... odd ... we spent tons of time fixing bugs in it.
look at the code yourself https://github.com/evilstreak/markdown-js/blob/master/src/dialects/gruber.js
-
Not really. It doesn't become an indented list until the second digit overflows left into the four spaces... Clearly this is being processed in the wrong order.
-
3<qqq>. This is a list.
5<qqq>. Random numbers are fun.
2<qqq>. (it's not really a list though...)
-
3<qqq>. This is a list.
5<qqq>. Random numbers are fun.
2<qqq>. (it's not really a list though...)
----------Nice <use> of <hidden> tags
:-P
-
It appears that Markdown processing happens earlier than tag removal.
4. Ah, found a quicker way to do it...
1. hello
\. And if I want \ as a 'number' i can have that too.