Morten Piibeleht

Sorry for not replying earlier -- I wasn't entirely sure how I felt about the proposal. In my opinion, you should just include the module docstring, e.g. as a last...

This is #921 as far as I can tell. The TL;DR is that, if you're using at-raw blocks, we can't really easily fix up file the references, so you do...

Broadly, I think this looks pretty good, and it would be great to have this option. Thank you for taking a stab at this! One thing that stands out to...

Just as a note: I think this would need to be implemented in IOCapture. Or, at least, IOCapture is relevant too, since we do do some ANSI code handling there....

> Would you be willing to merge it into Documenter.jl, to make sure it can stay up-to-date and well-maintained into the future? Unfortunately, I am not sure I would accept...

E.g. ``[`f(::Integer)`](@ref)`` can be used to refer to specific signatures. The `@ref` section in the docs should be updated to mention this possibility.

Good idea. It shouldn't be very hard to add methods that accept `Function` and `DataType` to `doctest`. Just need to construct the `Binding` and look up the docstring associated with...

> search index might be including the rendered html and that is why these codes are not working This is not the case, unless we are somehow pushing HTML into...

Yes, they should be keywords. We also got https://github.com/JuliaDocs/IOCapture.jl/pull/26 now, so it should be possible to pass these on pretty easily. One first step towards all that would be to...

Good timing. Maybe you can be the guinea pig for #2521 and see how well that PR works for your use case :slightly_smiling_face: