similar to: on R package vignette

Hi Dear R-users: I am building a R package and would like to create a generic variance function. Here is how I did var=function(x,...) { UseMethod("var") } I wrote a Rd file, put the R code in the right directory, and named var, var.default in the namespace. However, once I typed rcmd check , it gave me an error in S3-generic step. However, that error would not occur for mean and

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

Han-Lin I don't think I have seen a reply so I will suggest that maybe you could try a different approach than what you are thinking about doing. I believe the current best practice is to use the weights as a covariate in a regression model - and bytheway - the weights are the inverse of the probabilities of selection - not the probabilities. Fundamentally, there is a difficulty in making

Hi all, I was trying to create some vignette files for my newly developed package, however wondering whether there could be any simpler way to do so. In writing R extension it is advised to go through Sweave route, however I have already got a big pdf file and want to use this as package vignette. So far I have manually created the inst/doc folder in the main package skeleton, and put that file

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' ?

[Env: R 2.12.2, WinXp] In a vignette for the vcdExtra package, I had a text file, tv.dat under data/, that I used in the vignette as <<tv1,results=verbatim>>= tv.data<-read.table(system.file("data","tv.dat",package="vcdExtra")) head(tv.data,5) @ I was told that this now generates a warning for non-Rdata files in R CMD check. But I'm now

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:

On 09/12/2014, 10:36 PM, Yihui Xie wrote: > I took a look at the R source and I realized that the encoding was > actually never passed to the vignette engine: > https://github.com/wch/r-source/blob/e721ef5f4/src/library/tools/R/Vignettes.R#L507 > Apparently only the file and quiet arguments are passed to the > vignette engine. Did I miss anything? I think it's actually a little

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

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

On 18/12/2014, 12:17 AM, Yihui Xie wrote: > For the record, I saw a change had been made in R-devel: > https://github.com/wch/r-source/commit/d53b098 (Thanks, Duncan) > Meanwhile, I also made a change in knitr to assume UTF-8 unless R > passes an encoding to the vignette engine: > https://github.com/yihui/knitr/commit/23c6c8e2 Both will solve the > original problem, but

Dear R-users, I am trying to figure out why I cannot print vignettes in my new R installation (R.11 on opensuse 11.2). Apparently, vignette objects are properly created but could not be printed: > z<-vignette('grid') > str(z) List of 3 $ file : chr "/usr/lib/R/library/grid/doc/grid.Snw" $ pdf : chr "/usr/lib/R/library/grid/doc/grid.pdf" $ topic: chr

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

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

Hello, I am trying to run "RCMD check" on a package. It performs OK, with the exception of a single warning: * checking package vignettes in 'inst/doc' ... WARNING Package vignette(s) without corresponding PDF: AnnotationFuncsUserguide.Rnw As I understand the problem, the vignette is not built. However, I have no problems in doing so manually. How do I fix this problem? I

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"

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

I recently wrote a vignette, with the following at the top of the .Rnw file: %%\VignetteIndexEntry{How to use look up tables for h() functions} %%\VignetteDepends{sjedmin, spatstat} Using vExplorer() on this function, I got an error from this part of getVigInfo(): lines <- grep("^%[[:space:]]*\\\\Vignette", file) if (length(lines) == 0) stop("File ", vig,

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()

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