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.
Why are we shouting?
Anyway, don’t waste your time with “antivirus” software. That is not how you secure a system.
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…
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
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.