The Markdown format expects a space after whatever number of #s you put at the start, for it to be a corresponding level header.
Due to different parsers having different types of leeways, it becomes a bit difficult to make sure stuff always matches.
e.g. I was once mistaken about the way tabs work for multi-level bullets and numbering because GitLab had more leeway. Using discount, I realised where I was being wrong.
https://www.markdownguide.org/basic-syntax/
Putting a space is a good practice for compatibility because different software behaves differently. But the standard doesn’t specify it per se.
Your viewer must be parsing
#8as# 8.You’re free to not ‘waste time’ with anti-virus but I prefer the peace of mind.
You need to put a backslash before the hash tag. In Markdown a # is a headet
As Lojcs said…
The Markdown format expects a space after whatever number of
#s you put at the start, for it to be a corresponding level header.Due to different parsers having different types of leeways, it becomes a bit difficult to make sure stuff always matches.
e.g. I was once mistaken about the way tabs work for multi-level bullets and numbering because GitLab had more leeway. Using
discount, I realised where I was being wrong.The whole problem is because format doesn’t actually expects the space there, and it’s left to the interpretation of the parser
I thought the whole problem was that there was no de-facto standard and people kept on making their deviations while still calling it Markdown.
I personally like how Doxygen implements it.
No? There needs to be a space between on piefed and that’s how it works on github too.
https://piefed.social/comment/8602660
https://www.markdownguide.org/basic-syntax/
Putting a space is a good practice for compatibility because different software behaves differently. But the standard doesn’t specify it per se.