Hi Georgi,
Thanks for this pointer. My guess at this point is that I've found a bug
(or maybe a couple of bugs with 'utils::prompt()' and with the Rd to help
conversion), but let me know if you think otherwise.
I just did that way, and the usage lines that were generated by
'utils::prompt()' and
Hi Bill,
Sorry, I misunderstood the question.
To check if the problem is with R's tools, run
'utils::prompt(topic_long_table_header)" and see the usage section of the
generated file. Presumably, this should be the 'canonical way' to write the
usage entry for the function.
You can copy and past
Hi,
I receive the following warning when I check my package:
checking sizes of PDF files under ‘inst/doc’ ... WARNING
‘gs+qpdf’ made some significant size reductions:
compacted ‘gwqs-vignette.pdf’ from 458Kb to 162Kb
consider running tools::compactPDF(gs_quality = "ebook") on these files
Hi Georgi,
I'm not trying to use it as part of my documentation, it is one of my
function arguments. I want the function argument to be displayed correctly
in the help, but it is not. I'm curious how I should document the
"subsequent_page_notification" function argument in Rd.
Specifically, the
Rd is not LaTeX, although it resembles it. You should use only markup
described in WRE.
For example, \dots is for the use case you mention.
Georgi Boshnakov
-Original Message-
From: R-package-devel [mailto:r-package-devel-boun...@r-project.org] On Behalf
Of b...@denney.ws
Sent: 23
Dear All,
I updated my package DataVisualizations and get a note, only for
"r-release-osx-x86_64” and “r-oldrel-osx-x86_64”
Checking dependencies in R code ... NOTE
No protocol specified
Can anyone translate this note to me in a way that I know what the issue is?
Best Regards
Michael
Michael
Hello,
Does anyone know how to include verbatim \ldots (and maybe other LaTeX) in
an .Rd file correctly?
When LaTeX is in the default arguments for a function, the code is
interpreted which makes the documentation not match the default formal
arguments.
An example is:
https://github.c
