When resolving rmarkdown links to other packages, please do not anchor the link text.

[krivit]

Since #1633 was merged, the behaviour has been to expand [fun()] to \code{\link[pkg:fun]{pkg::fun()}}.

This is often unsightly and verbose and is not ideal when the link text refers to a class rather than its main constructor. For example, [`mcmc.list`] becomes \code{\link[coda:mcmc.list]{coda::mcmc.list}}.

I think it would be better if the link text were only anchored if the link is anchored. E.g.,

[fun()] -> \code{\link[pkg:fun]{fun()}}
[pkg::fun()] -> \code{\link[pkg:fun]{pkg::fun()}}

[krivit]

Further to this, package developers have relied on the old behaviour when writing their documentation: in those instances where we had intended to anchor the link text, we already have.

[krivit]

Apologies for bumping this. I've forked roxygen2 and patched rmarkdown to do what I describe, and it solves the problem for me, but I would appreciate a response from the maintainers what the behaviour will be going forward. I apologise in advance if this is the wrong venue to raise this.