Dear all,
I would like to draw you attention to this question on SO:
https://stackoverflow.com/questions/50372043/readlines-function-with-new-version-of-r
Based on the OP's code I used the script
###
create_matrix <- function() {
cat("Write the numbers of ve
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
---
Thanks for the report, fixed in R-devel 74782.
Please report back if the fix is not sufficient for your use case.
Tomas
On 05/23/2018 06:16 AM, Aaron Goodman wrote:
I noticed that scan.c does not yet support long vectors. It was causing a
problem in the rstan library (https://github.com/stan-de
Thanks for looking into this, empty string is the natural solution indeed.
Georgi
-Original Message-
From: Tomas Kalibera [mailto:tomas.kalib...@gmail.com]
Sent: 25 May 2018 10:05
To: Georgi Boshnakov; r-devel@r-project.org
Subject: Re: [Rd] Rd parser throws error for user macros invoke
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 'CHARS
Good day,
If there are S4 methods documented in an R package of the form
functionName,aVariableType,anotherVariableType-method
and some of the variable types have lengthy names and are defined in other
developers' packages, such as MultiAssayExperiment, the Index section of the
reference manua
