similar to: Rd2pdf error in R12.0

Hello everybody I'm am trying to build a pdf out of the Rd files that i wrote for a package, so that I can attach it to my thesis. if i Run Rd2pdf (or Rd2dvi) I get this error massage: Hmm ... looks like a package Converting Rd files to LaTeX . Creating pdf output from LaTeX ... Error in texi2dvi("Rd2.tex", pdf = (out_ext == "pdf"), quiet = FALSE, : Running

> The command Rd2pdf was rather useful for opening a package's manual > when you don't have access to the Internet (by using latex to pdf > conversion). However the way the function seems to operate changed at > version 2.14 of R. The noted changes listed on CRAN for this function > are as follows (which doesn't seem like it would affect my usage as > below): >

Hi, The following command: R CMD Rd2pdf --no-preview --output=./tmp.pdf --title=test genefu-package.Rd run against this file: https://hedgehog.fhcrc.org/bioconductor/trunk/madman/Rpacks/genefu/man/genefu-package.Rd (username: readonly; password: readonly) produces a very verbose error (see below) with R version 2.15.0 alpha (2012-03-07 r58622). The .Rd file has these lines in it: Version: \tab

Hi Peter, Duncan & Bert, Thank you kindly for the responses. Indeed, doc/NEWS.pdf is included in the source distribution, and then removed upon "make clean". I thought that it might be useful to report this for your benefit, but on closer inspection it appears that I'm getting errors that arise due to incompatibilities in my texlive and texinfo installations. This is the error

R Community, I often am in need of viewing the reference manuals of packages and do not have Internet access. I have used the code: path <- find.package('tm') system(paste(shQuote(file.path(R.home("bin"), "R")),"CMD", "Rd2pdf",shQuote(path))) someone kindly provided from this help list to generate the manuals from the latex files. This

Dear list, I am trying to produce a pdf manual using Rtools (version 3.1.0.1936) on Windows 8 (64-bit). I am also aware of the inconsolata issue posted in the forum (https://stat.ethz.ch/pipermail/r-devel/2013-June/066850.html), and then I have installed the patched version of R-3.0.1. However I still have some errors with the following message: R CMD Rd2pdf mypack Hmm ... looks like a package

Hello: 1. How can I tell when the development version of Rtools has changed? For the past few years, I've installed the development version of R tools with each new release of R. I encountered problems with this a few days ago, so I rolled back to Rtools212.exe. Unfortunately, I seem to have more problems with that version. My latest install was under Windows 7 Home Edition.

Hi, Due to a change in Rd.sty a few days ago (https://github.com/wch/r-source/commit/620eb9a#diff-3bf3d821c6faae50cd6ec931f6f63296L272), the default installation of TeXLive 2009 or 2012 no longer works when building Rd to PDF. The error log is like this: =============== Converting Rd files to LaTeX ..... Creating pdf output from LaTeX ... Error in texi2dvi(file = file, pdf = TRUE, clean = clean,

On 21/05/2017 10:30 AM, Peter Carbonetto wrote: > Hi, > > I uncovered a bug in installing R 3.4.0 from source in Linux, following the > standard procedure (configure; make; make install). Is this an appropriate > place to report this bug? If not, can you please direct me to the > appropriate place? Generally R-devel is better; I've responded there. > > The error

The nodes of our cluster do not have pdflatex installed. When running R CMD check there on a package with no errors in documentation, then R-2.13.0-alpha and R-2.12.2 report a possible error in Rd files, while R-2.11.1 did not. The platform is 64 bit CentOS. The output of R CMD check tree_1.0-28.tar.gz under the above three versions of R contains the following. R-2.11.1 stderr sh:

On a CentOS 7 machine, I am at a loss with respect to an inability to run a full R CMD check as anything involving tex files ends in tears. We followed the README at CRAN and installed a large number of tex-live packages on this machine. But when a manual is created, we end up with what follows below. Here, I chopped some of the error messages, the key seems to be 'Insufficient extension

Hi list, When using R CMD Rd2pdf, it is possible to set environment variable RD2PDF_INPUTENC to value "inputenx" and enjoy better support for UTF-8 characters (see ?Rd2pdf). This enables LaTeX package "inputenx" instead of "inputenc". Even better support for UTF-8 encoded characters can be had by better using the facilities provided by inputenx and making R CMD

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

Sorry for the noise. I assumed I could run this in the same directory as R CMD check. If I cd into the package dir, and run it like R CMD Rd2pdf man it works. I was a bit sleep deprived yesterday. The fact that the output starts by Hmm ... looks like a package threw me off. That output suggests it should work, I think. So I would suggests either 1) handling both package and man directories

Dear all, I am getting an R CMD check warning about the PDF manual. I am having a hard time finding out what is wrong, here is the log of the Rd2pdf call. The full check (and other) log is at https://api.travis-ci.org/jobs/46373922/log.txt?deansi=true if anybody is interested, and the package itself is here: https://github.com/metacran/r-builder/tree/bintex/rbuildertest Thanks, Best, Gabor

When I include the macros \packageAuthor, \packageDescription, \packageTitle, \packageMaintainer in a XX-package.Rd file, R CMD Rd2pdf fails with $ R CMD Rd2pdf mpra Hmm ... looks like a package Converting Rd files to LaTeX Error : mpra/man/mpra-package.Rd:6: file './DESCRIPTION' does not exist This does not happen if I comment out 4 occurrences of these 4 macros in mpra-package.Rd.

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, :

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

Hi all, Sorry if I seem a bit pissed because I am! Basically, I have written some script and I wanted to make a "documentation" for it using .Rd format. ############################################################################ I followed the example here in http://stat.ethz.ch/R-manual/R-devel/library/utils/html/prompt.html created the file plot.default.rd in my directory. But

R CMD build fails with recent R-devel because it is looking for texi2dvi in /usr/local/bin, but on this system, MacTex has installed it in /usr/bin. $ R CMD build IRanges * checking for file 'IRanges/DESCRIPTION' ... OK * preparing 'IRanges': * checking DESCRIPTION meta-information ... OK * cleaning src * installing the package to build vignettes * creating vignettes ... ERROR