similar to: formatR 1.0 caused error

This is an announcement of the release of an R package 'formatR', which can help us format our R code to make it more human-readable. If you have ugly (I mean unformatted) R code like this: ?# rotation of the word "Animation" # in a loop; change the angle and color # step by step for (i in 1:360) { ? # redraw the plot again and again

This is an announcement of the release of an R package 'formatR', which can help us format our R code to make it more human-readable. If you have ugly (I mean unformatted) R code like this: ?# rotation of the word "Animation" # in a loop; change the angle and color # step by step for (i in 1:360) { ? # redraw the plot again and again

Good morning folks: Made a second go at installing this and succeeded, but with some strange behaviours along the way. First the system back story. Using up to date edition Ubuntu 8.04 Using up to date edition of R 2.10.1 Using the Toronto, Ontario repository to draw from. After the first attempt ended up with two of the four dependencies installed so only the Rgtk related items would be

Hola: Me suena algo de que el año pasado alguien dijo algo sobre unas sugerencias de reglas de estilo para escribir código en R. No he oído nada más en esta lista (a lo mejor se me ha pasado por alto) Ayer se publicó un mensaje sobre esto precisamente en un blog en inglés: http://pairach.com/2012/06/06/r-style-guide/ (copiado debajo para facilitar la lectura y comentarios en esta lista)

In formatR 0.1-5, the dependency on the gWidgets and animation packages are removed. The GUI by gWidgets is optional now. Meanwhile, the function tidy.source() has been moved from the animation package to this package. > library(formatR) > tidy.source(textConnection(' # rotation of the word "Animation" # in a loop; change the angle and color # step by step for (i in

In formatR 0.1-5, the dependency on the gWidgets and animation packages are removed. The GUI by gWidgets is optional now. Meanwhile, the function tidy.source() has been moved from the animation package to this package. > library(formatR) > tidy.source(textConnection(' # rotation of the word "Animation" # in a loop; change the angle and color # step by step for (i in

I need some help understanding a problem running the tests on the 'digest' package. Initially, I got the message that the 'knitr' package was needed to run vignettes: Running vignettes for package ?digest? Error in loadVignetteBuilder(vigns$pkgdir) : vignette builder 'knitr' not found So I installed the knitr package and all its dependents (?mime?, ?stringi?,

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

I needed to clean someone else code and run it through tidy.source. It encountered a number of hangups which after some experimentation lead me to suspect that the culprit is # symbol when it is a part of literal string. For example if i copy the following to the clipboard confuse.tidy <-    function() {   txt <- 'abra # cadabra' } and run with default arguments >tidy.source()

Within an R session, type Sys.getenv() will list all the environment variables, but each one of them occupies about a page, so scrolling to find one is difficult. Is this because I don't know how to use it or something could be improved? Usually I'm not sure the exact name of a variable but want to look it up. Recently I installed rjags, with the JAGS-3.4.0's lib, include, modules

A few things to clarify: 1. You do not necessarily have to keep the \usepackage{} line if you use %\VignetteEncoding{UTF-8}, because Pandoc will use UTF-8 anyway in its LaTeX template. 2. Perhaps the vignette engine in R has done something clever to convert utf8 to UTF-8, but I'd recommend %\VignetteEncoding{UTF-8} instead of %\VignetteEncoding{utf8} to make sure it is a valid encoding name,

Hi list, Could anyone recommend some good website for formatting R code? For example, when you copy paste R code to gmail and back to R, it loses its format, the dash symbol causes errors. I've had someone used it to format my code here on the list, but can't find it anymore. Mike [[alternative HTML version deleted]]

Buenas, foreros y foreras; No sé si esto es pregunta para hacer acá, lo preguntaría en stackoverfow, si no fuese que el inglés me intimida. Quiero usar el packete `bookdown` para escribir un libro, pero resulta que la salida tiene que ser PDF y no lo consigo. Siguiendo las instrucciones de acá: https://bookdown.org/yihui/bookdown/get-started.html llego a compilar sin ningún problema en formato

Gracias por haberte tomado la molestia de indagar. Entiendo que es eso lo que hago en el encabezado YAML, basandome en la explicación del comienzo del punto 3 de acá: https://bookdown.org/yihui/bookdown/output-formats.html Eso mismo, con el documento que propone el propio Yihui (punto 1.2 del mismo libro) no lo consigo compilar a PDF. Y se me hace extrañísimo, porque tampoco me da error ni nada

Según lo entiendo yo, a mí no me funciona. Lo intenté hacer, también, en la consola directamente. Preferiría poder hacerlo en el documento Rmd, pero de momento ni uno ni otro consigo. Si compila lo hace al libro GitBook y listo. Parece imposible. 2018-07-17 20:02 GMT+02:00 Javier Marcuzzi <javier.ruben.marcuzzi en gmail.com> : > Estimado Juan Abasolo > > Yo no lo utilize pero leí

Gracias, Javier, por la paciencia. Soy malo explicándome. Ese ejemplo que me das, que es el que da Yihui Xie, es el que no consigo compilar si no es a GitBook (que es HTML). El mismo Yihui propone en el libro al que nos referimos los dos y el ejemplo en cuestión (referido en el apartado Get Started) modificar el código YAML para compilar en PDF. Efectifvamente, lo que quiero es conseguir que

Hi Yihui, Hi Duncan, I corrected my typo. Unfortunately knitr did not find my plots in the directory where they reside which is different from the Rmd document. The documentation of knitr says: base.dir: (NULL) an absolute directory under which the plots are generate root.dir: (NULL) the root directory when evaluating code chunks; if NULL, the directory of the input document will be used

Hi All, I have to compile a report for the management and decided to use RMarkdown and knitr. I compiled all needed plots (using separate R scripts) before compiling the report, thus all plots reside in my graphics directory. The RMarkdown report needs to access these files. I have defined ```{r setup, include = FALSE} knitr::opts_knit$set( echo = FALSE, xtable.type = "html",

Gracias, Victor. Tampoco es eso. Si saco la linea site: bookdown::bookdown_site Me sigue compilando en HTML, pero sin hacerlo en todos los capítulos si no solamente el del index.Rmd que tengo abierto. No puedo explicar cuanto me sorprende! Supongo que tendré algún puntito de alguna i que falta y al ponerlo me parecerá tontería. Pero ahora todavía es MISTERIO. 2018-07-18 11:03 GMT+02:00 Víctor

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