News for hackers. Stuff that matters.
Re:Moon's Mark Down (2016) by smoyer on Friday July 03, 2020 @10:07PM (#23729419)
This should be marked with [2016]. Personally, I've switched to ASCIIDoc (after looking at reStructured Text) because Markdown has too many variants and they don't consistently extend the markup the same way (a document that looks good in visual code fails to render in Github and vice-versa).
Re:Moon's Mark Down (2016) by wlkr on Saturday July 04, 2020 @07:43AM (#23731657)
If you don't mind me asking, what was the closest you came to finding a 'standard' Markdown? I use a subset frequently enough that it tends not to be an issue but there are times when, for example, embedding latex formatted math would be useful in a uniform manner.
Re:Moon's Mark Down (2016) by smoyer on Monday July 06, 2020 @08:23AM (#23747121)
Since we use Gitlab for private repositories and Github for public ones, the main irritation I find is that even those two aren't completely compatible. From a standards perspective, the "official" seems to be supported everywhere but when you start adding in "extensions/variants" all bets are off. You might be able to write most blog posts with the official version but I like TODO lists, tables, etc (without resorting to inline HTML).