Running R CMD roxygen on a big package can take quite a long time. It\'s obviously inefficient as well as it goes through everything regardless of whether a file has changed since the last roxygen cal
I am learning Roxygen and making good progress so far. I\'ve been able to document most of the package that I\'m working on, but I\'ve got a few places that I can\'t seem to get right. Please consider
Below I posted a mini example in which I want do write documentation for an “[“ method for a S4 class. Does someone know how to properly document a method for the generic \"[\" using roxygen and S4?
I have a simple shell script that builds my Roxygen documents, builds the package, checks, then installs the newly built package on my machine. It\'s quite simple:
The default value of a parameter of my function contains a \"%\". This seems to be a problem for roxygen, it produces a lot of warnings and R CMD check fails when trying to build latex documentation.
I\'m writing an R package that\'s going to be used by others, so I\'m trying to get this one right!I want to use roxygen for documentation and RUnit for unit testing, but I haven\'t used them b开发者_
Is it possible to include .R files in the data directory of my package in the roxygen process? I have put several .R files in the data directory. When they are sourced with data(), they read in raw d