Gábor Csárdi

It should appear in an "Inherited active bindings" section, like the "Inherited methods" section, but you are right, that does not happen currently.

The methods are listed recursively, so it will be the same for active bindings.

Right. We'll probably need to have some additional information to know 1) whether to create those links, and 2) where they should point to.

> just stating something like "see field foobar" both seem suboptimal So what would be optimal in your opinion?

AFAICT the sphinx example does not say anything about public fields at all.

> It's implicit. The arguments to the constructor are what end up as public fields. Well, you can already do this in roxygen2, just leave out the `@field` tags completely....

The block for the method is not an `\examples{}` block, because there can be only one. The reason for having the one at the end is that otherwise `R CMD...

OTOH it seems like a waste to use a single `` as the title in an Rmd, there is already a title after all? But if most `.Rmd`s are like...

I think if the options are set temporarily in #1091 then that takes care of the cleanup as well, no? I.e. if you want an option for all Rmds you...

> There's much more state than options to clean up. I know, but knitr does not do that in general, and I am not sure if it is our job...