In Windows, cmd.exe is a command line shell, not a terminal/console host application, ConHost.exe is the correct application, and is now officially called Windows Console, and does not support programming ligatures, however, the new Windows Terminal does support programming ligatures, and includes support for it with cmd.exe, as cmd.exe itself does not implement this functionality.
* Add crosh (ChromeOS terminal) to Works list
Was disappointed to find that Fira Code is not supported by crosh, based on this readme. In fact, it's not acknowledged at all, so I scoured the web for a solution - and found one in this repo's wiki.
* Lowercase Crosh -> crosh
As Rawgit is closing example links will stop to function at the end of October 2019. I've chosen jsdelivr over unpkg as it's using GitHub as a source like Rawgit, rather than NPM, and have a bigger [market share](https://w3techs.com/technologies/comparison/cd-jsdelivr,cd-unpkg). Related issue #18.
It's a Markdown Editor (https://github.com/brrd/Abricotine) that switches to Fira Code as soon as the font is installed, ligatures are fully supported.
A rendering of the “Terminal support” table was broken in `README.md`.
The [new GitHub's parser][1] seems to handle differently the leftmost empty
table cell if it has no leading pipe (`|`):
* if it's in the middle of the table, the whole row shifts to the left
(the second cell becomes first, third takes place of the second, etc.)
* if it's the table's last row or all rows after it also have only whitespace
and no leading pipe, they are parsed as a new block element
(the code block, because of leading whitespace)
Also, new spec [recommends][2] adding leading and trailing pipes for
_“clarity of reading”_ and to avoid parsing ambiguity. Both currently existing
tables were updated to follow this advice.
[1]: https://githubengineering.com/a-formal-spec-for-github-markdown/
[2]: https://github.github.com/gfm/#tables-extension-
