Gábor Csárdi

You need to start the method documentation with `@details` or `@description`, though, so this is not strictly a bug.

> Is there no way around that? There is, and we will do it soonish. It needs some internal changes in the roxygen parser, so it is not super easy....

Maybe we can fix this. Can you provide a reproducible examples please? See https://github.com/r-lib/roxygen2/blob/master/.github/SUPPORT.md#making-a-reprex

According to my comments at https://github.com/r-lib/roxygen2/blob/357d856f6ccdb96b7a95b42bf747cf10e2a26fb3/R/markdown-escaping.R#L13-L16 this should work. But it does not. It is probably not _that_ hard, because we already escape these macros, so they are already parsed.

Yeah, so I think for this we need to add another mode to the `roxygen_parse_tag()` C function, to only parse the first argument of `\if` or `\ifelse` and leave the...

We'll look at this issue before the next release, yes.

We can help you best if you show us an example that we can run. Is your package open source? Is it available at GitHub or elsewhere?

Yeah, we if the output is `"github_document"` then we could parse it as markdown, as usual, and then we would not use the link regex on the code chunks. I...

There is at least this issue, and it would be great to support chunk options (https://github.com/r-lib/roxygen2/compare/feature/knitr-chunk-options) and I also want to look at whether we can generate HTML formulas with...

We'll have inheritance from super or other classes etc. eventually. Unfortunately this requires rewriting much of the current inheritance implementations. > Link to R6? [Processor$run] Yeah, this would be awesome,...