similar to: What does \Sexpr[results=rd]{} exactly mean in Rd?

Hi (Duncan?), The other day I noticed some characters will cause errors in R CMD CHECK because of parse_Rd(), and AFAIK, these chars include '%', '{' and '}'. For example, note the comments in the example section: %~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~% \name{testfun} \Rdversion{1.1} \alias{testfun} \title{ A Test } \description{ A test } \usage{ testfun() } \value{ NULL }

Hello, Here's an example that renders correctly using Rd2txt / Rd2latex / R CMD Rd2pdf, but has problems under Rd2HTML: \name{foo} \title{foo} \section{foo}{ This should be on a separate paragraph This should be on a separate paragraph This should be on a separate paragraph \Sexpr[stage=render,results=rd]{ paste( rep('Sexpr: This should be on a separate

Dear developers, I came across with a bug while parsing Rd files. Given is the following minimal Rd file: ---- \name{foo} \title{foo} \description{ #ifdef windows win #endifd #ifdef unix unix #endif } ---- By accident I have a typo at line 6, instead of having #endif I typed #endifd. If I run checkRd(), parse_Rd(), Rd2HTML(), or others including the command line "R CMD Rconv" R

I've just committed some fairly big changes to R-devel. - There's a new tag \Sexpr which allows R code to be embedded within the Rd file, similar to Sweave, \RdOpts corresponds to \SweaveOpts. - The parser now mainly issues warnings, rather than errors, in case of syntax errors. It throws away a few tokens and tries to restart. This should let you see most of your errors in

[This email is either empty or too large to be displayed at this time]

While on the topic of Rd macro arguments, it seems that if a multiline argument is supplied, the lines after the first are silently ignored: f <- tempfile() mac6 <- "\\newcommand{\\mac6}{mac6: #1}" cat(mac6, "\\mac6{2*3 2+2 sin(pi) }\n", file = f) rd <- tools::parse_Rd(f) > rd mac6: 2*3 --- Georgi Boshnakov -----Original Message----- From: Tomas Kalibera

Bug or feature? I get the following error from parse_Rd() when a user Rd macro (including system ones) is invoked with empty argument {}, eg \mymacro{}: Error in tools::parse_Rd(fn) : Value of SET_STRING_ELT() must be a 'CHARSXP' not a 'NULL' A full example is further below with the system macro \CRANpkg{}. In this example it doesn't make sense to use empty argument but

With a pretty recent version of R 2.11.0 (devel,unstable, svn 50178) on Linux I could not install version 1.5-8 of zoo (the current on on CRAN): % R-devel CMD INSTALL -l Rlib3 zoo * installing *source* package 'zoo' ... ** R ** inst ** preparing package for lazy loading ** help *** installing help indices converting help for package 'zoo' finding

Hi all, Currently Sweave does not format the (especially numeric) value in \Sexpr{}, and I often have to round() the numbers explicitly, otherwise I will get more than 10 digits, which is not necessary for me in most cases. Is there a way to specify the number of digits to be kept for values in \Sexpr{}? e.g. can we make \Sexpr{} respect getOption('digits')? Thanks! Regards, Yihui --

Hi, I am doing a small experiment to test if I can use MathJax ( official site: http://www.mathjax.org ) in R's html help pages (i.e. options(help_type='html')) and it seems working with some minor modifications. The screenshot (rendered by Firefox 4.0 beta and with STIX fonts) of the help page in html format with MathJax enabled is at the following url:

Hi. I am having difficulty making \Sexpr work as desired. Specifically, the pdf and the text versions of the help system differ, and I can't reproduce the example on page 63 of the R Journal article by Murdoch and Urbanek (Vol 1/2, December 2009). Is there an example package that I could examine for Best Practice? thanks -- Robin Hankin Uncertainty Analyst hankin.robin at gmail.com

Hi all, I am trying to use \Sexpr{} within \examples{} in the manual, and it all works fine, except that I get an error and then a NOTE from R CMD check when it checks for long lines in the manual. The long line check calls `Rd2txt` with fragment = TRUE, because it only checks the \usage{} and \examples{} sections, but fragment = TRUE does not evaluate \Sexpr{}, and then an unevaluated \Sexpr{}

No, I do not get the same as you. I have tested with R-devel and R-patched compiled today. When I do R CMD Rd2pdf mpra I get (as reported a few days ago) Hmm ... looks like a package Converting Rd files to LaTeX Error : mpra/man/mpra-package.Rd:6: file './DESCRIPTION' does not exist whereas you (Kurt) reports that this works on zTree. When I do R CMD Rd2pdf mpra/man I get - a

I've just committed code that allows R to be built with support for dynamic help pages using \Sexpr in Rd files. Define USE_NEW_HELP and the R function tools:::.convertRdfiles will be used instead of the Perl RdConv script, supporting \Sexpr and using the new R converters. Currently only text help has the macros evaluated when the user asks for help; the others are rendered at install

When I run R CMD Rd2pdf on the man pages of a package, ie R CMD Rd2pdf man I get Converting Rd files to LaTeX Warning in parse_Rd("man/mpra-package.Rd", encoding = "unknown", fragment = FALSE, : man/mpra-package.Rd:6: unknown macro '\packageTitle' Warning in parse_Rd("man/mpra-package.Rd", encoding = "unknown", fragment = FALSE, :

I was writing Rd documentation for a new package when I came across this issue. Here's the smallest example: > library(tools) > cat("\\examples{x <- '<%=rnorm(1)%>'}\n",file=file.path(tempdir(),'test.Rd')) > readLines(file.path(tempdir(),'test.Rd')) [1] "\\examples{x <- '<%=rnorm(1)%>'}" >

Hi everyone, >From the currently available version of the package VBmix, I would like to retrieve the intermediate .tex file that generates the VBmix-manual.pdf file. Formerly, running R CMD check with --no-clean allowed to get this tex source from a hidden directory : this feature was removed, but can apparently still be accessed through R CMD Rd2pdf --no-clean. Surprisingly, while the

Do I understand correctly that we don't want Rd files to be valid latex ? This seems odd to me. I see that `tools::parse_Rd()` doesn't like `\verb!foo!` so maybe roxygen2 is actually doing the right thing (as opposed to just trying to) ? `parse_Rd() ` is probably what I need indeed, for some reason I hadn't found it, so that should fix my own issue here thanks a lot. Le ven. 21 juil.

I am in the process of submitting a package to CRAN. R CMD check ran successfully on the package on my local computer, using R version 2.1.1. However, on the computers for CRAN (with version 2.10.0), the following errors occurred: Warning in parse_Rd("./man/predict.Rd", encoding = "unknown") : ./man/predict.Rd:28: unknown macro '\dquote' *** error on file

Thanks for the report, I am testing a patch that will allow multi-line arguments to user macros. Best Tomas On 05/25/2018 04:45 PM, Georgi Boshnakov wrote: > While on the topic of Rd macro arguments, it seems that if a multiline argument is supplied, the lines after the first are silently ignored: > > f <- tempfile() > mac6 <- "\\newcommand{\\mac6}{mac6: #1}" >