Displaying 20 results from an estimated 7000 matches similar to: "parse_Rd raises error when example section contains a quoted percent character"
2009 Apr 07
2
parse_Rd() Version 2 on Japanese Vista 32 (encoding problems)
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.0Alpha English XP Pro 32 works fine without any
2009 Jun 20
2
Special characters in Rd example section will cause errors
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
}
2006 Aug 31
1
Overriding InitTempDir
For embedded projects, one may want to eliminate the per-session temp
directory created by InitTempDir() and just use a system-specific temp
directory. Here's my solution:
extern char *R_TempDir;
void my_InitTempDir()
{
char *tmp;
if (R_TempDir){
if (rmdir(R_TempDir) != 0){
perror("Fatal Error: could not remove R's TempDir!");
2009 Oct 30
1
parse_Rd and/or lazyload problem
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
2017 Oct 04
1
R CMD Rd2pdf and macros
No, I do not get the same as you.
I have tested with R-devel and R-patched compiled today. When I do
R CMD Rd2pdf mpra
I get (as reported a few days ago)
Hmm ... looks like a package
Converting Rd files to LaTeX Error : mpra/man/mpra-package.Rd:6: file
'./DESCRIPTION' does not exist
whereas you (Kurt) reports that this works on zTree.
When I do
R CMD Rd2pdf mpra/man
I get
- a
2017 Oct 03
2
R CMD Rd2pdf and macros
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, :
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
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
2011 Oct 17
1
What does \Sexpr[results=rd]{} exactly mean in Rd?
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 not to be true.
2012 Nov 04
1
Rd2pdf freeze
Hi everyone,
>From the currently available version of the package VBmix, I would like to
retrieve the intermediate .tex file that generates the VBmix-manual.pdf
file.
Formerly, running R CMD check with --no-clean allowed to get this tex
source from a hidden directory : this feature was removed, but can
apparently still be accessed through R CMD Rd2pdf --no-clean.
Surprisingly, while the
2023 Jul 21
1
tools::parseLatex() crashes on "\\verb{}"
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.
2009 Jul 08
2
\dQuote in packages
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
2014 Nov 12
4
Problem with build and check
I am getting failure of build and check, for an Rd file that has a long argument list.
Guess diagnosis: a quoted string beyond a certain point in the argument list is fatal.
Example: Use the function below, create an Rd file for it with prompt(). Move the .Rd
file to the man directory (no need to edit it) and try building
dart.control <- function(server=c("production",
2023 Jul 21
1
tools::parseLatex() crashes on "\\verb{}"
? Fri, 21 Jul 2023 15:14:09 +0200
Antoine Fabri <antoine.fabri at gmail.com> ?????:
> On a closer look it seems like roxygen2 introduces those, when using
> markdown backtick quoting, if the quoted content is not syntactic. For
> instance:
>
> #' `c(c(1)`
> #' `c(c(1))`
>
> Will convert the first line to `\verb{c(c(1)}` and the second to
>
2011 Mar 18
1
[Patch suggestion] Adding 3rd arg to tempfile() to set extension
The other day I was working on an example which used tempfile() to create
file for use by the graphics device. And while I love tempfile()---as it is
portable and clever and the files get cleaned by R and all that---I noticed
one missing feature I would like to see: beside a starting name pattern, and
an optional directory, an 'file extension' argument would be nice to have.
As e.g. in
2012 Feb 21
1
tempdir() documentation or real bug ?
?tempdir says
By default, ?tmpdir? will be the directory given by ?tempdir()?.
This will be a subdirectory of the temporary directory found by
the following rule. The environment variables ?TMPDIR?, ?TMP? and
?TEMP? are checked in turn and the first found which points to a
writable directory is used: if none succeeds ?/tmp? is used.
Unfortunately, it doesn't seem to
2017 Apr 25
4
tempdir() may be deleted during long-running R session
>>>>> Dirk Eddelbuettel <edd at debian.org>
>>>>> on Sun, 23 Apr 2017 09:15:18 -0500 writes:
> On 21 April 2017 at 10:34, frederik at ofb.net wrote:
> | Hi Mikko,
> |
> | I was bitten by this recently and I think some of the replies are
> | missing the point. As I understand it, the problem consists of these
> |
2008 Oct 16
1
Rscript -e, Sweave and tempdir()
Hello R-Help
I have a question about the "behind the scenes" behaviour of the Rscript -e command and particularly its interaction with Sweave and tempdir().
We are trying to deploy R as a web service to do water quality analyses and have been writing software to call Sweave via Rscript eg:
cmd> Rscript -e Sweave('sweavefile.Rnw')
One problem we have been having is that
2017 Apr 26
6
tempdir() may be deleted during long-running R session
On 26/04/2017 4:21 AM, Martin Maechler wrote:
>>>>>> <frederik at ofb.net>
>>>>>> on Tue, 25 Apr 2017 21:13:59 -0700 writes:
>
> > On Tue, Apr 25, 2017 at 02:41:58PM +0000, Cook, Malcolm wrote:
> >> Might this combination serve the purpose:
> >> * R session keeps an open handle on the tempdir it creates,
>
2008 Aug 29
2
Security issue with javareconf script (PR#12636)
Full_Name: Tom Callaway
Version: 2.7.2
OS: Fedora 10 (Linux/x86_64)
Submission from: (NULL) (96.233.67.230)
Recently, Debian identified a security issue with the javareconf script in R. I
confirmed that this is still unfixed in R 2.7.2.
The following patch resolves the issue:
diff -up R-2.7.2/src/scripts/javareconf.BAD R-2.7.1/src/scripts/javareconf
--- R-2.7.2/src/scripts/javareconf.BAD