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.
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.
Yeah. The power of MD is that it’s lightweight, versatile, and not very restrictive. You don’t need to remember a lot, and the parser is dirt easy to implement.
The negatives are that it’s not very restrictive, nobody remembers what’s what, and the parser so easy to implement, everyone and their dog has one, and they’re all slightly different
Why are we shouting?
Anyway, don’t waste your time with “antivirus” software. That is not how you secure a system.
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
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.
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.
Yeah. The power of MD is that it’s lightweight, versatile, and not very restrictive. You don’t need to remember a lot, and the parser is dirt easy to implement.
The negatives are that it’s not very restrictive, nobody remembers what’s what, and the parser so easy to implement, everyone and their dog has one, and they’re all slightly different
Yes, but projects like Wayland which are trying to do this get shouted down.
I was almost sure Wayland had succeeded… Well except for people still stuck on Xorg because of accessibility features…