Morten Piibeleht

For (1), you should be able to do it with `doctest(MyModule, manual = false)`. (2) would indeed be nice to have.

It should work fine if the line starting with "may" gets indented to the third character.

It it true that it's not consistent with CommonMark, as far as I can tell. But the parser in Base is often not following CommonMark anyway. So at best it's...

The code block should be indented to three (as opposed to 4) spaces as well, then it works. The parser in Base is apparently really picky about whitespace.

There's a [Markdown syntax section](https://docs.julialang.org/en/stable/manual/documentation/#Markdown-syntax-1) in the manual, but it is not this detailed.

> I wonder if using CommonMark.jl for parsing would make things a bit more robust for this? Almost certainly. It's on my wishlist (actually, in general allowing alternative parsers), but...

I think the discussions in #839 might be relevant for this, even though they are more about at-docs blocks. In fairness, I am not sure that the at-refs should match...

Actually, I am not 100% what is being asked here: @rafaqz Documenter doesn't know how to parse and run Weave blocks. So I am not really sure how we could...

Do you just use them as input for Documenter? Then the standard Julia flavored Markdown that we write the documentation in. I wouldn't look at Weave at all. Or do...

> So would github, hugo, or pandoc markdown be best? No idea, to be honest, needs to be tested. Markdown being Markdown, they all have some subtle differences. On the...