Displaying 3 results from an estimated 3 matches for "mac6".
Did you mean:
mac
2018 May 25
2
Rd parser throws error for user macros invoked with empty argument
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: Ge...
2018 Jun 01
0
user macros with multi-line arguments in Rd (was Re: Rd parser throws error for user macros invoked with empty argument)
...tch 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}"
>
> 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: Toma...
2018 May 14
3
Rd parser throws error for user macros invoked with empty argument
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