;
>> There may be legitimate reasons to evaluate everything in the namespace, but
>> I've no idea what they are. Incidentally, Rstudio also does 'mget' on the
>> whole package namespace and triggers bindings during auto
t;
>> There may be legitimate reasons to evaluate everything in the namespace,
>> but I've no idea what they are. Incidentally, Rstudio also does 'mget'
>> on the whole package namespace and triggers bindings during
>> autocomplete. https:/
roxygen2 can be fragile when there are mistakes in preceding
roxygen2 documentation blocks, or conflicting documentation blocks
elsewhere in a package, and, if I remember correctly, extraneous empty
lines. A lack of verbose options or logging makes debugging roxygen2 errors
tricky sometimes. Try pu
You can leave them in R/ (and write them as functions) but use
.Rbuildignore to exclude them from the distributed package. People can use
the source, eg github, to regenerate the package and all its data if they
wish. This way, R CMD check and tests can cover them easily while
developing.
However,
I have a fair number of medical words and acronyms in my icd9 package
and found aspell to be very useful. For an example, look in the icd10
branch in github at https://github.com/jackwasey/icd9/tree/icd10 .
Look in .aspell/ and R/generate_spelling.R.
On Tue, Mar 1, 2016 at 12:29 PM, Duncan Murdoch
Thanks for all your input. I am now aware that the R environment
running configure will have set R_HOME. I had sometimes been running
./configure without R_HOME set, leading to my problem (since in this
case, the configure snippet does assume 'R'). I'll stick to the
official build routine from now
nation
of what I think is happening may help you guide me.
Best wishes,
Jack
On Saturday, September 26, 2015, Dirk Eddelbuettel wrote:
>
> On 26 September 2015 at 10:27, Jack Wasey wrote:
> | Having just read section 1.2 in Writing R extensions, a fragment of a
> | configure script
Hello,
Having just read section 1.2 in Writing R extensions, a fragment of a
configure script is offered in order to determine the correct compiler
options. It starts by setting R_HOME with:
: ${R_HOME=`R RHOME`}
`R` is called, even if, as in my case, `Rdevel` is the command used to
invoke pack
