Morten Piibeleht

My feeling is that the doctests should be a bit separate from the other at-blocks. One reason for this is that you want doctests to be as self-contained as possible....

Definitely something we could consider. Should be a non-default option of a doctest I think. It will make the doctest execution much slower. Is there some API that would allow...

> I'd even argue that in strict mode (default), referencing a file that does not exist should throw an exception. I agree that this would be ideal. I am wondering...

Saying that it's in a docstring should be doable (i.e. we should have that information). Line numbers are trickier though, since, if I remember correctly, the Markdown parser does not...

> But at some point that `MarkdownAST.Link` gets created starting from a docstring; at that point we should still be able to know where the docstring came from. So we...

I am not necessarily against this, and I think it's a use case we should support. However, I wonder if could re-use the at-eval block somehow, without having to create...

I am hesitant to just rely on the the `show` methods like at-example does. In particular, for `Markdown.MD`, that I think would change the behaviour. Right now, we incorporate the...

> I took a more careful look at what this function does for travis and github actions, and I just can't think of a good analog for the simple SSH...

> I really don't like user prompts as it wreaks havoc with automation. I suppose I could add an option to the SimpleSSHConfig struct that makes it possible to do...

There's no support for pushing tags locally at the moment though?