Displaying 3 results from an estimated 3 matches for "rdconv2".
Did you mean:
rdconv
2018 Jul 12
3
Top level \Sexpr and R CMD check
On Thu, Jul 12, 2018 at 2:21 PM Duncan Murdoch <murdoch.duncan at gmail.com> wrote:
> I think I found the bug. The tools::checkRd function only processes
> \Sexpr's with "stage=render". I think the author (who might have been
> me, I forget) assumed that would imply all the earlier stages as well,
> but apparently it doesn't.
>
> So you could use that as
2018 Jul 12
1
Top level \Sexpr and R CMD check
...>> Seems like there is no clean workaround here.
>>
>> Thanks again,
>> G.
>
> Btw. would it make sense to just allow \Sexpr as a top level section?
> Maybe here:
> https://github.com/wch/r-source/blob/98e9999eb0e8616550632a1675e4d2dbe630d5e4/src/library/tools/R/RdConv2.R#L500-L503
>
> At least if stage=render, there is no way to check if the returned
> value is always a valid top level section, anyway.
> If it is not a valid section (or \Sexpr returns some bad markup in
> general), then the user gets a render-time error,
> but with stage=render...
2018 Jul 12
0
Top level \Sexpr and R CMD check
...the whole section is dropped.
>
> Seems like there is no clean workaround here.
>
> Thanks again,
> G.
Btw. would it make sense to just allow \Sexpr as a top level section?
Maybe here:
https://github.com/wch/r-source/blob/98e9999eb0e8616550632a1675e4d2dbe630d5e4/src/library/tools/R/RdConv2.R#L500-L503
At least if stage=render, there is no way to check if the returned
value is always a valid top level section, anyway.
If it is not a valid section (or \Sexpr returns some bad markup in
general), then the user gets a render-time error,
but with stage=render I guess one cannot do better....