similar to: edit(vignette(...))

I apologize that these questions are stupid and literal. I write to ask for clarification of comments in the R extensions manual about vignettes. I'm not great at LaTeX, but I'm not a complete novice either, and some of the comments are puzzling to me. 1. I'm stumbling over this line: "Make sure all files needed to run the R code in the vignette (data sets, ...) are accessible

I am trying to re-organizing my Makefile for testing my R packages and I am having trouble finding a structure I like. The problem seems to be that "R CMD check", which does wonderful things, does not allow dependency information to flow through very gracefully. That is, since everything is copied into the pkg.Rcheck directory, it is difficult to make any changes to source files without

( A similar problem is also reported by Sebastian P. Luque with library(maptools) library(trip) in the vignette as below ). I am writing a vignette which loads RMySQL and RPostgreSQL. This produces the warning: Loading required package: DBI Warning in .simpleDuplicateClass(def, prev) : A specification for class ?dbObjectId? in package ?RPostgreSQL? seems equivalent to one from package

Dear list, we have a markdown vignette for our package in vignette/vignette.md This is not visible from within R with the vignette(package = "mypackage") command. I assume the reason is that the vignette function only shows PDF vignettes. Is there any way to circumvent this and display markdown vignettes directly from within R? I tried to seek the answer from R archives and search

I think the online order of vignette files are not based on vignette title or filename alphabetically. I am just curious: by what order these vignette files were displayed online so I can make changes accordingly? Thanks, Zhu -----Original Message----- From: Duncan Murdoch [mailto:murdoch.duncan at gmail.com] Sent: Friday, March 04, 2016 10:47 AM To: Wang, Zhu; r-devel at r-project.org Subject:

From R-help ... >I notice that you have the IPSUR package loaded; you know, just a >shot in the dark here, but did you try not loading it? > >I ask because the vignette is built by making a special choice for >set.seed, and the workspace that ships with the package might be >interacting in an unexpected way. Is it possible that a package can save a set seed and have the effect

Full_Name: Chris Evans Version: 2.3.1 OS: Windoze XP Submission from: (NULL) (217.34.100.197) If I give "vignette("introduction")" I get: Error in sprintf(gettext(fmt, domain = domain), ...) : use format %s for character objects vignette() works for some other vignettes and "vignette()" gets me a list of vignettes and shows three with the name

I?m preparing a package (fastR) for submission to CRAN, but the vignette index keeps going AWOL, or at least R CMD check ?as-cran thinks so. I?ve tried several things and gave myself the weekend to think of other things, but I can?t figure it out. Perhaps someone on the list can lend a hand. Here?s one example situation, where I build the index.html file myself and put it in inst/doc/index.html

[Env: Win Xp / StatET 2.0 / R 2.15.0] In my heplots package I extended the HE-examples.Rnw vignette under inst/doc. The package passes R CMD check on my machine: * using log directory 'C:/eclipse-3.7/heplots.Rcheck' * using R version 2.15.0 (2012-03-30) * using platform: i386-pc-mingw32 (32-bit) ... * checking sizes of PDF files under 'inst/doc' ... OK * checking installed files

Dear all, I'm trying to use a Markdown vignette with UTF-8 encoding. It compiles well when knitting the vignette in RStudio, but it fails to recognize the UTF-8 settings when building the source package. Can someone point out what I'm doing wrong? I tried to put the relevant information below. Best regards, Thierry Details: Using 64-bit R 3.1.2 with encoding = "native.enc"

Hello: Clicking "Knit Word" in RStudio 0.99.893 with R 3.3.0, works fine with a vignette with "output: word_document". However, "R CMD build" throws the following error: $ R CMD build pkgW2vignettes * checking for file ?pkgW2vignettes/DESCRIPTION? ... OK * preparing ?pkgW2vignettes?: * checking DESCRIPTION meta-information ... OK * installing the

In ?Sweave, it refers to Sweave User Manual. In the doc folder of utils package, I see "Sweave.pdf". However, I can't find it from within R > vignette("Sweave User Manual") Warning message: vignette ?Sweave User Manual? not found > browseVignettes("utils") No vignettes found by browseVignettes("utils") > library(help=utils) does not

Dear R-devel, Question: How can I get Sweave to recognize that the \thebibliography section is already created and generate the vignette pdf with a single pass? Or is there a way to let R CMD build know that Sweave needs to be run twice? If (1) is not possible, any suggestions how to auto-generate a crude generic bibtex .bib file from my existing document? Background: I maintain

Hi, this is tangentially related to the recent discussion on vignettes. vignette() currently produces a listing of available vignettes, but these are not clickable. Since R has a browseURL() function, it seems natural to have a version that produces HTML with clickable links. Here's an attempt at that: source("http://dsarkar.fhcrc.org/R/vignette-browser.R") browseVignettes()

Dear colleagues, I am having issues trying to build a R package I recently wrote. I am using R 2.14.0 and my package depends on another package called aod. Running: R CMD Sweave vignette.Rnw is perfectly fine and the vignette compiles properly. but when I use R CMD build mypackage to build the tar.gz I get the following error: * installing the package to re-build vignettes * creating

I have packages where I know CRAN and other test platforms do not have all the resources to build the vignettes, for example, access to databases. Previously I think putting BuildVignettes: false in the DESCRIPTION file resolved this, by preventing CRAN checks from attempting to run the vignette code. (If it was not this, then there was some other magic I don't understand.) Now, when

On 09/12/2014, 4:38 PM, ONKELINX, Thierry wrote: > Dear Yihui, > > I have created a reproducible example at https://github.com/ThierryO/utf8vignette > > The \usepackage{} line is needed, otherwise R CMD check --as-cran will give a warning. > %\VignetteEncoding{UTF-8} did not solve the problem. I've just taken a look at the sources, and that's only in R-devel, it never

Dear Duncan, The UTF-8 characters aren't properly rendered in the pdf version of the vignette. $?? ????? ?????? ?????? ????? ?? ?? is rendered as $????? ?????????? ???????????? ????? ?????? ? ???????? ???????? The same problem occurs when I use render("vignette.md", output_format = "mypackage::mystyle"), instead of render("vignette.md", output_format =

Trying to Stangle / Sweave a file $ cat vignette.Rnw %\VignetteEngine{knitr} \documentclass{article} \begin{document} \end{document} results in a misleading error message: ~/tmp$ R CMD Stangle vignette.Rnw Error: Vignette engine package not specified Execution halted when what is missing is the full specification knitr::knitr; 'vignette engine package and function not specified' ?

Hi, all-- I've been working on a doParallel package to provide a foreach parallel backend for the new parallel package, but I am having trouble building the vignette. On my system, if I use the following minimal vignette (call it buggyVignette.Rnw): \documentclass[a4paper]{article} \title{Sweave Example 1} \author{Rich Calaway} \begin{document} \maketitle In this example