Speaking of markdown text quote. . placeholder
-
```#text markdown text quote```
```#text markdown text quote ```
-
That's because
```foo```is inline code andfoo
is a block of code.
-
And you explanation about language type text hinting?
-
inline code doesn't have the language hinting thing
-
Stop defending the polished turd.
-
Stop defending the polished turd.
Yes, stop doing that! Do something more constructive ... like applying more polish!
Preferably in Karate Kid style: Wax On, Wax Off, Wax On, Wax Off
-
But why is the first word (markdown) bolded?
markdown text quote
-
Yes, stop doing that! Do something more constructive ... like applying more polish!
Preferably in Karate Kid style: Wax On, Wax Off, Wax On, Wax OffAin't nearly enough wax for this one.
-
It thinks that's nginx configuration or something.
-
-
Why are you putting a
#in front of the language?markdown not boldedvar x = 123; function() { return x; }Doesn't look like a bug to me.
-
The bug report is the same text producing different results based on whether or not you put a newline there.
-
That was explained above. One is the block format, which we have adopted from github flavored markdown. The other is inline and doesn't support a language hint.
-
- Why are you treating the ``` differently
- Why aren't you accepting the language hints
- Why is markdown bold
-
Language hints are not accepted in inline code blocks. This is how github flavored markdown for fenced code blocks works.
Markdown is bold because the hints were not correct established. You put a pound sign in front of the language hint for some reason.
