search for: chunkprefix

...=============================================================== --- src/library/utils/R/SweaveDrivers.R (revision 56193) +++ src/library/utils/R/SweaveDrivers.R (working copy) @@ -390,6 +390,8 @@ } if (options$include) { + if (grepl("[[:space:]]", chunkprefix)) + chunkprefix = shQuote(chunkprefix, type = "cmd") cat("\\includegraphics{", chunkprefix, "}\n", sep = "", file = object$output) linesout[thisline + 1L] <- srcline Thanks! Regard...

...ition_wide.dta") @ ... ---------------------------------------------- It can be compiled using "Sweave.sh foo.Rnw", but when I tried "Sweave.sh -c foo.Rnw", I got error message: "...Processing code chunks ... 1 : term hide Error in data.frame(chunk = options$label, chunkprefix = chunkprefix, : arguments imply differing number of rows: 0, 1" I thought it might be an imcompatibiltiy problem between the cacheSweave and the foreign packages, but the problem was still there when I tried to read the data in using "read.table" function. Any ideas? Many thanks...

...iges Paket: stashR A Set of Tools for Administering SHared Repositories (0.3-3 2009-03-26) > Sweave("cacheSweaveExample.rnw", driver=cacheSweaveDriver) Writing to file cacheSweaveExample.tex Processing code chunks ... 1 : echo term verbatim Fehler in data.frame(chunk = options$label, chunkprefix = chunkprefix, : arguments imply differing number of rows: 0, 1 The solution is to use named code chunks as in this corrected example: <<a, cache=true>>= a=1 @ <<b>>= a+1 @ The problem is that the cacheSweave driver tries to store the label of a code chunk, along wit...

Dear Sweave users, Could you help me to find a way to place Sweave output files in a subdirectory of the currentfolder without giving them a subname? If the option "prefix.string=foo/" is used, all files are placed in this folder, but begin with an hyphen-minus, which makes it difficult to work with them. If the option "prefix=FALSE" is used, then files won't be placed in

...ice=pdf} or \SweaveOpts{grdevice=cairo_pdf} trying to plot something simple <<fig=T, echo=T>>= plot(1:10,1:10,main='Some title') @ would result in an Sweave error: 18:16:47.299: 1 : term verbatim 18:16:47.308: 2 : echo term verbatim pdf pdf 18:16:47.391: Error in dev(name = chunkprefix, width = options$width, height = options$height, : 18:16:47.392: unused argument(s) (name = chunkprefix) 18:16:47.393: Calls: Sweave -> <Anonymous> -> dev 18:16:47.396: Execution halted Systemcall.cpp(238): Systemcall: 'Rscript --verbose --no-save --no-restore "/usr/local/sh...

R has had the ability to generate pdfs with transparent colors for a couple of years now using pdf(..., version="1.4"). By default, Sweave uses just 'pdf' (without version 1.4), so a hack is needed when using Sweave to create pdfs with transparent colors. See http://tolstoy.newcastle.edu.au/R/help/04/11/6655.html I would find my work process simpler if R defaulted to

...\")", after=epsline1) epsline2 <- grep("options\\$fig && options\\$eval", runcodesrc) runcodesrc <- append(runcodesrc, deparse(quote( if (options$emf && .Platform$OS.type == "windows") { grDevices::win.metafile(file=paste(chunkprefix, "emf", sep="."), width=options$width, height=options$height) err <- try({SweaveHooks(options, run=TRUE) eval(chunkexps, envir=.GlobalEnv)}) grDevices::dev.off() if(inherits(err,...