search for: parse_rd

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, : man/mpra-package.Rd:9: unknown macro '...

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...

.... 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)%>'}" > parse_Rd(file.path(tempdir(),'test.Rd')) Error in parse_Rd(file.path(tempdir(), "test.Rd")) : Unexpected end of input (in ' quoted string opened at test.Rd:1:17) In addition: Warning message: In parse_Rd(file.path(tempdir(), "test.Rd")) : newline within quoted string at t...

...r Daniel Hansen writes: > > Interesting. When I take e.g. zTree as the last CRAN package using the > \packageTitle macro, > > R CMD Rd2pdf zTree > > seems to work fine, but > > R CMD Rd2pdf zTree/man > > gives > > Converting Rd files to LaTeX Warning in parse_Rd("zTree/man/zTree-package.Rd", > encoding = "unknown", : > zTree/man/zTree-package.Rd:6: unknown macro '\packageTitle' > Warning in parse_Rd("zTree/man/zTree-package.Rd", encoding = "unknown", : > zTree/man/zTree-package.Rd:9: unknown...

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 [mailto:tomas.kalibera at gmail.com] Sent: 25 May 2018 10:05 To: Georgi Boshnakov; r-devel at r-project.org Subject: Re: [Rd] Rd parser throws error for user macros invoked with empty argument Thanks f...

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 } \author...

Hi, I need some help with 2.9.0 parse_Rd() Version 2 changes. I read the .pdf file and some posts on r-help, but after playing with this for several hours, I can't seem to get around this UTF-8 problem. - I'm trying to get rid of some warnings during R CMD Check for R 2.9.0Alpha on Japanese Vista 32 - The same setup on a R 2.9.0...

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 ./man/predict.Rd Error : ./man/predict.Rd:28: Unrecognized macro \dquote Warning in parse_Rd("./man/print.Rd", encoding = "unknown") : ./man...

...urprisingly, while the manual generation runs with no warnings when issuing "R CMD check --as-cran VBmix_0.2.9.tar.gz", "R CMD Rd2pdf VBmix_0.2.9.tar.gz" collapses under warnings, until it simply freezes... A sample : VBmix_0.2.9.tar.gz:30918: unexpected '{' Warning in parse_Rd("VBmix_0.2.9.tar.gz", encoding = "unknown", fragment = FALSE, : VBmix_0.2.9.tar.gz:30921: unexpected '}' Warning in parse_Rd("VBmix_0.2.9.tar.gz", encoding = "unknown", fragment = FALSE, : VBmix_0.2.9.tar.gz:30929: unexpected '{' Warning...

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. 2023 ? 16:18, Ivan Krylov...

...ents, 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 [mailto:tomas.kalibera at gmail.com] > Sent: 25 May 2018 10:05 > To: Georgi Boshnakov; r-devel at r-project.org > Subject: Re: [Rd] Rd parser th...

Thanks for the report and the examples - and they do not have to be that verbose, it is enough to just define and use a command, e.g. cat("\\newcommand{\\mac1}{MAC1:#1}\\mac1{}", file=f) rd <- tools::parse_Rd(f) Whenever you get an error message like "Value of SET_STRING_ELT() must be a 'CHARSXP' not a 'NULL'", there is a bug (at least the error message should be relevant/informative). I am testing a patch that will allow empty arguments to macros (they will expand to an e...

...lly valid R code. When something that is not valid R is given in a Markdown code block, roxygen2 should not output \code{}, so it outputs \verb{}. Also, unlike in LaTeX as understood by tools::parseLatex(), \verb{} blocks use the {} braces in R documentation, and are understood correctly by tools::parse_Rd(). Perhaps you also need tools::parse_Rd()? -- Best regards, Ivan [*] https://developer.r-project.org/parseRd.pdf

I'm encountering problems when making lazy-loadable databases of the output from 'parse_Rd'. The lazy-load database is of seemingly limitless size when I try to reload it... Admittedly I am using functions that I'm not really supposed to use, which is why this isn't a bug report, but there does seem to be something strange going on; my code is very similar to code that lives...

Hi R-devels, I noticed that you are working quite actively on the new Rd-parser and have made it the default renderer in R-2.10.0dev. So I would like to come back on an issue I have already raised on this list last November ("Two minor escaping issues using \preformatted{....} in Rd format") My setting has slightly changed as \preformatted, AFAICS is not supported within \describe

Hi, I have spent a few hours on the R-exts manual and the documentation of parse_Rd() (as well as the PDF document in the references), but I still have not figured out what results=rd means. I thought I could use an R code fragment to create an Rd fragment dynamically. Here is an example, in which I was expected the output to be a describe list <DL> in HTML, but it turns out...

...ttes --timings BioSeqClass_1.7.0.tar.gz Warning: unknown option '--no-vignettes' Warning: unknown option '--timings' Converting Rd files to LaTeX ... BioSeqClass_1.7.0.tar.gz Warning in readLines(f) : incomplete final line found on 'BioSeqClass_1.7.0.tar.gz' Warning in parse_Rd("BioSeqClass_1.7.0.tar.gz", encoding = "unknown", fragment = FALSE, : BioSeqClass_1.7.0.tar.gz:2: unexpected UNKNOWN '\?' Warning: BioSeqClass_1.7.0.tar.gz:1: All text must be in a section Warning: BioSeqClass_1.7.0.tar.gz:2: All text must be in a section Warning: B...

...mmy?: * checking DESCRIPTION meta-information ... OK Warning: newline within quoted string at dart.control.Rd:11 Warning: /tmp/RtmpjPjz9V/Rbuild398d6e382572/dummy/man/dart.control.Rd:46: unexpected section header '\value' Warning: newline within quoted string at dart.control.Rd:11 Error in parse_Rd("/tmp/RtmpjPjz9V/Rbuild398d6e382572/dummy/man/dart.control.Rd", : Unexpected end of input (in " quoted string opened at dart.control.Rd:88:16) Execution halted Session info for my version > sessionInfo() R Under development (unstable) (2014-10-30 r66907) Platform: i686-pc-lin...

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

...12:46:37 -0400 writes: > > Proposed patch > > Thank you Ben! > > > [the rest is technical nit-picking .. but hopefully interesting > to the smart R-devel reader base:] > > There was a very subtle thinko in your patch which is not easily > diagnosed from R's parse_Rd(): > > Error in parse_Rd("/u/maechler/R/D/r-devel/R/src/library/stats/man/delete.response.Rd", : > Unexpected end of input (in " quoted string opened at delete.response.Rd:78:63) > In addition: Warning message: > In parse_Rd("/u/maechler/R/D/r-devel/R/src/libr...