similar to: R CMD check for the R code from vignettes

Interesting, yesterday I had exactly this problem, but today I solved it (see the R-pkg-devel list) by _installing_ R-devel and > update.packages(checkBuilt = TRUE) I also tried it on Martin's Fedora 26 example below. Worked fine (had to install some packages...) On ubuntu 16.04. G?ran Brostr?m On 2017-12-06 11:29, Martin Maechler wrote: >>>>>> Pearce, Robert

In Section 1.4.2 of "Writing R Extensions" %\VignetteEngine{knitr::knitr} should be %\VignetteEngine{knitr::knit} > sessionInfo() R version 3.0.2 (2013-09-25) Platform: x86_64-apple-darwin10.8.0 (64-bit) Is this sort of thing best reported here, or is a huge report in order? John Maindonald email: john.maindonald at anu.edu.au phone : +61 2 (6125)3473 fax

Hi, as far as I understand it, the new R devel feature of processing non-Sweave vignettes will (a) locate any "[.][RrSs](nw|tex)$" or ".Rmd" files, (b) check for a registered vignette engine, (c) process the file using the registered "weave" function, (d) and possibly post process the generated weave artifact (e.g. a *.tex file). I'd like to propose to extend

Hello List, while dealing with a questin of 'xiaodao' ( http://r.789695.n4.nabble.com/Problem-with-large-small-numbers-in-knitr-tp4653986.html) I noticed that copying the default inline hook function obtained by knit_hooks$get("inline") into a knit_hook$set(inline = <...>) call turns off exponential fomatting in the resulting .tex file. I used a stripped version of

I have problems with very large numbers using knitr. In the following, my a and b are extremely small and ssrr and ssru are extremely large. Knitr delivers error messages. Scaling ssrr and ssru by 1000 resolved the problem: ssrr <-ssrr/1000 ; ssru<-ssru/1000 Any clue as to how I might resolve the problem? BTW, the same program does run in another computer. I am wondering whether my

I am resubmitting this bug report but with additional information. I am running this with windows 10: w64-mingw32 with R Under development (unstable) (2017-12-04 r73829). I build 'httk' from the command prompt using 'R CMD build httk' after installing the required packages. Then when the vignettes are being created, it crashes. Today I installed the latest versions of Rtools,

So far you haven't provided a reproducible example yet. I wonder what exactly the object `sample_analysis` is. Sounds like it is an environment. If that is the case, devtools::build_vignettes() will tangle (for the meaning of "tangle", see ?tools::buildVignette) your vignette into an invalid R script. Environments cannot be represented via dput(), so knitr's purl() (eventually

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

Hello, I'm trying to rebuild a package (using R version 3.3.2 (2016-10-31)) that has not seen any changes since it was last built without problems in previous R versions. It fails during vignette building with: ---<--------------------cut here---------------start------------------->--- $ R CMD build diveMove * checking for file ?diveMove/DESCRIPTION? ... OK * preparing ?diveMove?: *

I have two questions about packaging up code. 1) Weave/tangle advisable? In the course of extending some C code already in S, I had to work out the underlying math. It seems to me useful to keep this information with the code, using Knuth's tangle/weave type tools. I know there is some support for this in R code, but my question is about the wisdow of doing this with C (or Fortran, or other

>>>>> Pearce, Robert <Pearce.Robert at epa.gov> >>>>> on Tue, 5 Dec 2017 21:31:09 +0000 writes: > I am resubmitting this bug report but with additional information. I am running this with windows 10: w64-mingw32 with R Under development (unstable) (2017-12-04 r73829). There is no such message (as you cite below) in the R-devel archives:

As a user, I am always annoyed beyond measure that Sweave vignettes precede the code by a command line prompt. It makes running examples by simple copying of the commands from the vignette to the console a pain. I know the idea is that it is clear what is the command, and what is the output, but I'd rather precede the output with some kind of marking. Is there any other solution possible /

Robert, To expand a bit on Goran's point, is it possible that you have an old library with packages installed that your R-devel is hitting. The R headers changes relatively recently, so any packages with compiled code that were built long enough ago (I don't have the exact date off the top of my head) need to be rebuilt before they can be safely used. If this is happening in a state

I am working with Sweave and would like to print out into my latex document the result of the R command version$platform So what I first tried in my .Rnw document was \Sexpr{print(version$platform)}. However, the output from this command is the string "x86_64-apple-darwin10.8.0" (without the quotes). This contains an underscore, which is a special character in tex and so I get an error

Now that R 3.0.0+ supports non-Sweave vignettes, R-exts \S 1.4.2 seems to imply that it is possible to include both Sweave and knitr vignettes in a single package. I'm wondering if anyone has tried this and/or if there are some hidden gotchas putting this into practice, and concerned about creating problems with CRAN checks if I try this. Consider two vignettes: pkg/vignettes/vign1.Rnw,

Hi everyone, I am using package knitr, FIRST TIME. I don't have access to RStudio. Read through Yihui's page, didn't find it helpful. Stuck on terms Rnw, GFM (GitHub Flavored Markdown). Never used Sweave, so the reference is not helping. Is there a simple step-by-step example WITHOUT RStudio? My question: What is the procedure? The documentation explains the functions, but does

I thought some of you might be amused by this. In my non-work time, I'm an avid weaver and teacher of weaving. I'm working on a project involving creating many detailed weaving patterns, so I wrote R code to automate it. Details here: http://stringpage.com/blog/?p=822 If the overlap between R users and avid tablet weavers turns out to be >> 1, I'll polish it up and turn it

I'm learning to use R/Sweave/LaTeK to write my stat reports. Is there a way to have an executive summary in the beginning while still having the analysis code embedded? For example, a study has three independent objectives so I want my report to have three sections. Ideally the code chunk that answers the first objective would be embedded in the first section and so on.

On 21/02/17 19:06, Sebastian P. Luque wrote: > Hello, > > I'm trying to rebuild a package (using R version 3.3.2 (2016-10-31)) > that has not seen any changes since it was last built without problems > in previous R versions. It fails during vignette building with: > > ---<--------------------cut here---------------start------------------->--- > $ R CMD build

Hi, Could R-Core consider adding 'RtangleRuncode' and 'RtangleFinish' to the exports of utils. Their weave equivalent 'makeRweaveLatexCodeRunner' and ?'RweaveLatexFinish' are exported, as well as the other tangle utility functions 'RtangleSetup' and 'RtangleWritedoc'. The rationale is not just symmetry. ;-) I'm finishing a small package that