My GitHub repository has nothing but a readme in it. In this readme, locally I wrote this:
Factoids:
- There are about six different ways to do everything in Forked.
- There are actually six different ways to enter loops.
- There are six directionals and six I/O commands.
- 666. ha.
Emphasis on the last line.
What GitHub decided to show was not 666
.
DCLXVI
is the Roman Numeral number for 666.
This really creeped me out. My local file and the raw file both show 666
.
What is GitHub doing, and why is the indentation on the un-numbered list messed up? Is this an easter egg, or some satanic bug?
Best Answer
This seems to be followed by github/markup issue 991, where on ordered sub-list, decimal numerals automatically turns into roman numerals.
As mentioned in "A formal spec for GitHub Flavored Markdown", GitHub markdown spec GFM: GitHub Flavored Markdown Spec is built on top of the CommonMark Spec.
And as Tommi Kaikkonen mentioned in his answer, the ordered list is because of the dot following 666. See GFM Spec section 5.2.
As mentioned in section 6.1, any ASCII punctuation character may be backslash-escaped, to avoid this issue.
That means:
(as explicitly shown in ForNeVeR's answer)
That is why that
666
number is changed to roman numerals in a GitHubREADME
markdown.Mike Lippert commented:
However, no: it shows
dclxvi
, because the generated html code is<ol start="666">
, which is consistent with the GFM specs:(here, '
666
' is the ordered list marker)Mike adds:
You get an ordered list
<ol>
within an un-ordered list item<li>
:GitHub CSS rules include:
If you put
3em
, you would getinstead of