I tried to create a package using some functions and scripts I created (using X11 on a Mac). While R CMD check was doing its work, it encountered a problem as follows:
temp = trim(unlist(strsplit(lp.add(ranefterms[[i]]),
+ "\+")))
Error: '\+' is an unrecognized escape in character string starting "\+"
The oddest thing, however, is that my function actually does NOT have “\ +”. Instead, it has “\ \ +” (see below). So I don’t know why “\ \ +” is recognized as “\ +”.
for(i in 1:n)
temp = trim(unlist(strsplit(lp.add(ranefterms[[i]]), '\\+')))
To dig a little further, I looked at the packageName-Ex.R file in the Rcheck folder. As it turned out, all the “\ \”s have been changed to “\” in the checking process (e.g., the double slashes I need for functions such as strsplit() and grepl())
I wonder what may have been the cause of it. Sorry that I can’t come up with a reproducible example…
The offending code comes from the Examples section of one of your help files (which is why it ends up in
packageName-Ex.R). To fix it, just escape each of the backslashes in the Examples sections of your*.Rddocumentation files with a second backslash. (So, type\\to get\in the processed help file, and type\\\\to get\\.)Unless it’s escaped,
\is interpreted as a special character that identifies sectioning and mark-up macros (i.e. commands like\author,\description,\bold, and\ldots). Quoting from Duncan Murdoch’s Parsing Rd files (the official manual for this topic):As an example of what this looks like in practice, here is part of
$R_SOURCE_HOME/src/library/base/man/grep.Rd, which is processed to create the help file you see when you type?grepor?gsub.In the processed help file, it looks like this: