search for: vignetteindexentry

Hi, I have a problem when checking the package 'probdistr' (on probability distributions). I got this warning * checking index information ... WARNING Vignettes with missing or empty \VignetteIndexEntry: [1] "probdistr-chi" "probdistr-contextra" "probdistr-discrete" [4] "probdistr-discrextra" "probdistr-exp" "probdistr- finitesupp" [7] "probdistr-gaussian" "probdistr-general" "probdistr-...

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...

...n with my R package, but it seems that there is no model to copy among those packages that I have installed in my R. Has anybody used Sweave for package vignettes? I have run into some minor inconveniences, where I would appreciate hints: - I cannot find out in R-exts manual how to actually write \VignetteIndexEntry so that it would be incorporated into 00Index.dcf. Should you put the entry within braces (LaTeX way) or use colon or something before the entry (00Index.dcf instructions)? Actually, I cannot get much of an 00Index.dcf: If I use --force to build the package, the 00Index.dcf will be replaced wit...

...Both packages use knitr to convert Rnw to PDF. mosaic also uses R.rsp to include static PDFs. $ grep -i vig mosaic/DESCRIPTION VignetteBuilder: knitr, R.rsp [09:22][rpruim at Mac21521:~/projects/github] $ grep -i vig fastR/DESCRIPTION VignetteBuilder: knitr $ grep Vig mosaic/vignettes/*Rnw %\VignetteIndexEntry{mosaic resources} %\VignettePackage{mosaic} %\VignetteKeywords{mosaic, vignettes, resources, references} %\VignetteEngine{knitr::knitr} $ grep Vig fastR/vignettes/*Rnw fastR/vignettes/Errata.Rnw:%\VignetteEngine{knitr::knitr} fastR/vignettes/Errata.Rnw:%\VignetteIndexEntry{Errata} fastR/vignett...

...y browseVignettes("utils") > library(help=utils) does not refer to any vignettes. The vignette does not appear in the main page for utils in help.start(). I checked the source code for the Sweave vignette, but I don't see anything wrong. It has all of the required elements: %\VignetteIndexEntry{Sweave User Manual} %\VignettePackage{utils} %\VignetteDepends{tools} %\VignetteDepends{datasets} %\VignetteDepends{stats} Am I accessing it incorrectly, or is there something wrong in my install of R-2.15.1? > sessionInfo() R version 2.15.1 (2012-06-22) Platform: x86_64-pc-linux-gnu (64-bit)...

...d by R CMD check. However after installing the package (in my personal R library location) doing vignette('rcdk') says Warning message: vignette 'rcdk' *not* found But I can see the PDF file located under rcdk/doc in the R library directory. The header of the Rnw file is % \VignetteIndexEntry{rcdk Tutorial} % \VignettePackage{rcdk} % \VignetteKeywords{} I am totally stumped by this - could anybody shed some light on what I'm doing wrong? Thanks, ------------------------------------------------------------------- Rajarshi Guha <rguha at indiana.edu> GPG Fingerprint: D070...

...d). The vignettes and the index.html files exist and vignette() as well as browseVignettes() work as expected. I have not found anything about this in NEWS or "Writing R extensions", which says: "At install time an HTML index for all vignettes is automatically created from the \VignetteIndexEntry statements unless a file index.html exists in directory inst/doc. This index is linked into the HTML help system for each package." Have I missed something? Thanks a lot Thomas Petzoldt -- Thomas Petzoldt Technische Universitaet Dresden Institut fuer Hydrobiologie thomas.petzo...

>>>>> On Fri, 29 Oct 2004 12:47:46 +0200 (CEST), >>>>> S J Eglen (SJE) wrote: > 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)...

...in /inst/doc, and have the others that should be rebuilt in /vignettes. This would include any that use "private R packages, screen snapshots, ...", or in my case one that takes just a little short of forever to run. 3. Do these unprocessed package also contribute to the index via \VignetteIndexEntry lines, or will I need to create a custom index? Terry Therneau

Hi R-devel, [Question]: * Is there a KEYWORDS file to lookup 'keywords' to supply the vignette command, '\VignetteKeywords{}'? -or, is the pkg writer free to tag the vignette using any keywords he/she chooses? i.e., free-tagging. Thank you, + Elliot Kleiman __________________________ San Diego State University http://www.sdsu.edu/

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:

...;Sweave, Part II: Package Vignettes" by Friedrich Leisch. I am using a windows XP machine (other session info below). Here is what I have done. 1) I add the 'inst/doc' directory to the package source tree. 2) I have added the following information in the preamble of the .Rnw file % \VignetteIndexEntry{An \texttt{R} Package for Miscellaneous Psychometric Analyses} % \VignetteDepends{MiscPsycho, statmod} % \VignetteKeyword{misc} 3) I then copy the file "MP.Rnw" to the 'inst/doc' directory. 4) I then run Rcmd build g:\MiscPsycho The process begins as usual and it even tries to c...

...ing the devtools package. The build command is R --vanilla CMD build "myPackage" --no-manual --no-resave-data The DESCRIPTION file has VignetteBuilder: knitr Suggests: knitr Imports: rmarkdown The markdown vignette YAML contains vignette: > %\VignetteEngine{knitr::rmarkdown} %\VignetteIndexEntry{The title} \usepackage[utf8]{inputenc} The custom output style converts the markdown to beamer with the --latex-engine = xelatex flag. The vignette in tar.gz passes R --vanilla CMD check --timings --as-cran * checking files in 'vignettes' ... OK * checking for unstated dependencies in...

...uot;") becomes: vignetteMetaRE <- function(tag) paste("[[:space:]]*%+[[:space:]]*\\\\Vignette", tag,"\\{([^}]*)\\}[[:space:]]*", sep = "") Details: The test package I'm using has only one vignette: \documentclass[oneside,letterpaper,12pt]{book} %\VignetteIndexEntry{some entry} %\VignetteDepends{stats} %\VignetteKeyWords{mymodel} %\VignettePackage{testpkg} \begin{document} <<test>>= print("test") @ \end{document} R CMD build, R CMD check and R CMD INSTALL run successfully. If I add an extra space after %\VignetteDepends{stats} then &quo...

On 09/07/2018 3:24 PM, Witold E Wolski wrote: > Dear Yihui, > > Thank you for the valuable questions. > > sample_analysis is a "tibble" while > configuration is an "R6" class. > But I also have parametrized reports where I pass R reference classes > as arguments. > > This is the Rmd yaml params part corresponding to the error message. > >

...la CMD build "myPackage" --no-manual > --no-resave-data > > The DESCRIPTION file has > > VignetteBuilder: knitr > Suggests: knitr > Imports: rmarkdown > > The markdown vignette YAML contains > vignette: > > %\VignetteEngine{knitr::rmarkdown} > %\VignetteIndexEntry{The title} > \usepackage[utf8]{inputenc} > > The custom output style converts the markdown to beamer with the --latex-engine = xelatex flag. > > The vignette in tar.gz passes R --vanilla CMD check --timings > --as-cran > > * checking files in 'vignettes' ... OK &g...

...ocument}. See the LaTeX manual or LaTeX Companion for explanation. Type H <return> for immediate help. ... l.9 \begin {document} ? -------------- TEX FILE ------------------ % \VignetteIndexEntry{GeneSpring contents} % \VignetteDepends{GeneSpring} % \VignetteKeywords{Interface} % \VignettePackage{GeneSpring} \documentclass{article} \usepackage{C:/PROGRA~1/SILICO~1/GENESP~1/data/rw1081/share/texmf/Sweave} \begin{document} \author{Thon de Boer} \title{Using R with GeneSpring} \maketitle...

...gt;> The DESCRIPTION file has >>> >>> VignetteBuilder: knitr >>> Suggests: knitr >>> Imports: rmarkdown >>> >>> The markdown vignette YAML contains >>> vignette: > >>> %\VignetteEngine{knitr::rmarkdown} >>> %\VignetteIndexEntry{The title} >>> \usepackage[utf8]{inputenc} >>> >>> The custom output style converts the markdown to beamer with the --latex-engine = xelatex flag. >>> >>> The vignette in tar.gz passes R --vanilla CMD check --timings >>> --as-cran >>&gt...

...lla CMD build "myPackage" --no-manual --no-resave-data > > The DESCRIPTION file has > > VignetteBuilder: knitr > Suggests: knitr > Imports: rmarkdown > > The markdown vignette YAML contains > vignette: > > %\VignetteEngine{knitr::rmarkdown} > %\VignetteIndexEntry{The title} > \usepackage[utf8]{inputenc} > > The custom output style converts the markdown to beamer with the --latex-engine = xelatex flag. > > The vignette in tar.gz passes R --vanilla CMD check --timings --as-cran > > * checking files in 'vignettes' ... OK >...

...at FGCZ.ETHZ.CH" date: "`r Sys.Date()`" output: pdf_document: default html_document: default params: configuration: !r quote(get(data(skylineconfig, package="myPackage"))) data: !r quote(get(data(sample_analysis, package="myPackage"))) vignette: > %\VignetteIndexEntry{Summarize Peptide Level Measurements} %\VignetteEngine{knitr::rmarkdown} %\VignetteEncoding{UTF-8} --- ```{r setup, include=FALSE} library(tidyverse) knitr::opts_chunk$set(echo = FALSE, message=FALSE) data <- eval(params$data) configuration <- eval(params$configuration) ``` Have a gre...