Consider switching to GitLab-Flavoured Markdown #1

Closed
opened 2020-09-11 22:49:31 -04:00 by eggy · 2 comments
Owner

Because of the massive headache that is managing Pandoc with both python-markdown-math’s and GitLab’s styles, it might be easier to just revert to GitLab-Flavoured Markdown and be done with it. Both parsers support that format relatively painlessly.

Because of the massive headache that is managing Pandoc with both `python-markdown-math`'s and GitLab's styles, it might be easier to just revert to GitLab-Flavoured Markdown and be done with it. Both parsers support that format relatively painlessly.
Author
Owner

The problem with doing so is that GitLab Markdown is incompatible everywhere. We can look at this again after a week or so.

The problem with doing so is that GitLab Markdown is incompatible everywhere. We can look at this again after a week or so.
eggy added the
general
label 2020-09-12 11:43:49 -04:00
Author
Owner

For my sanity, screw this.

For my sanity, screw this.
eggy closed this issue 2020-09-12 11:45:44 -04:00
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: eggy/eifueo#1
No description provided.