Dear All,
TL;DR: Is there a way to get a full traceback and/or frame dump for
errors that occur in build-time and install-time \Sexpr{} calls in R
documentation files?
# Context
I am working on a package (
https://github.com/joycecheng/ergm/tree/ergm-term-index ) whose
documentation includes a
ng one of the dependency
> mechanisms that the language provides, i.e. the clean solution.
>
> Duncan Murdoch
>
> On 10/07/2020 7:51 p.m., Pavel N. Krivitsky wrote:
> > Dear All,
> >
> > I would like to have two packages that do not depend on each other
> > th
Dear All,
I would like to have two packages that do not depend on each other that
have an identical generic to be able to dispatch to each other's (non-
conflicting) methods. If it is of interest, the background for why this
is needed is given at the end of this e-mail.
As it is, it looks like tw
Dear All,
I have a package (ergm, in case you are wondering) that has some low-
level routines (say, low()) that produce messages that the end-user
needs to see and that tend to be called multiple times for every time
the top-level routine (say, high()) is called, often by other routines
that are
