80. Mark down “—” maakt een Header aan en#

In mijn teksten verschen vaak onverwachte layouts, en dat lijkt aan de -- te liggen.
Maar ik zag dat een # ook verantwoordelijk is voor verandering van de layout.

“—” creates a header

“—” is valid markdown - in most (there isn’t a one true standard, after all) markdown flavours. However,

And just to be perfectly clear, I don’t think that there’s anything wrong with that, supporting more formatting can be great. But I also think care should be taken to not break previous content when markup changes are introduced. (Ie. I think old content should either be processed as the old markup that it is, or converted to the new markup)

(the backslash escape I even mentioned in

backslash-escaped literal “—” fits my use better.

Hm, we haven’t changed our Markdown parser recently (though a few of its dependencies may have changed, so that might be the cause). However, what you’re seeing is valid Markdown, so I’m not sure the code needs to change. You can test it here on Discourse:

this is a header
---
this is the body

becomes

this is a header

this is the body

There are a couple ways you could fix the syntax to get what you want, including

this is a header
\---
this is the body

which becomes

this is a header

—

this is the body

or

this is a header

---

this is the body

which becomes

this is a header

this is the body

If you want, I can just replace all of the --- in your observations and comments with one of those two options. Just let me know which one you prefer.

https://github.com/TlaskalV/iNaturalist_app
https://labenvmicro.shinyapps.io/iNaturalist_app/

Posted on January 29, 2021 06:05 PM by ahospers