similar to: Devtools 0.7

# devtools The aim of `devtools` is to make your life as a package developer easier by providing R functions that simplify many common tasks. Devtools is opinionated about how to do package development, and requires that you use `roxygen2` for documentation and `testthat` for testing. Future version will relax these opinions - patches are welcome! You can track (and contribute to) development of

# devtools The aim of `devtools` is to make your life as a package developer easier by providing R functions that simplify many common tasks. Devtools is opinionated about how to do package development, and requires that you use `roxygen2` for documentation and `testthat` for testing. Future version will relax these opinions - patches are welcome! You can track (and contribute to) development of

cross-posting announcement to R-Announce, R-devel and R-package-devel. The R Consortium recently announced (https://www.r-consortium.org/news/blogs/2016/08/r-consortium-funds-three-projects-july) support of the R Documentation Task Force. The task force aims to design and implement the next generation documentation system for R. We aim to take the best from the many attempts to improve

I have a package that I'm developing that I need to unload the library. Long story short I figured out that the leaving the compiled code loaded lead to a segmentation fault, but unloading the code will fix it. I've read the documentation and it appears that there are several ways to do this? What is the popper accepted current standard for unloading compiled code? The options as I

I'm not sure if this is the official behavior but I would expect the na.action function applied to a lm object to return the na.action. Here is what I mean. > x<-0:10 > y<-x+rnorm(10) Warning message: In x + rnorm(10) : longer object length is not a multiple of shorter object length > y[5]<-NA > m<-lm(y~x) > m$na.action 5 5 attr(,"class") [1]

I'm having a problem with the error and warning functions. I've tried this on multiple machine so I'm fairly sure it's not machine dependent and I've tried it on the latest versions 2.6.0-2.7.1. Whenever my program gets to an error or warning it crashes the entire program rather than throwing the error like it should. Here are the relevant bits. ... char const * const

I'm developing packages with CUDA, and I'm running into a problem with memory allocation. Since CUDA involves memory on the GPU device it requires that the program handle memory allocation and deallocation separately from R. The simplest case of allocating a char and then deallocating causes a segmentation fault when R closes. Not on garbage collection but only on exit. Is there

hi Andrew Many thanks for the suggestion. I gave it a try , but still get the same issue - a fresh Rgui window (just one) opens, with an empty .RData, when I submit a script ( Ctrl & F8 ). I also tried running things as administrator, but it made no difference. Apparently windows 7 is selling like hot buns, so there should be enough market pressure before too long , to encourage the

https://github.com/NV/chrome-devtools-autosave doesn’t play nice with Asset Pipeline. https://github.com/NV/chrome-devtools-autosave/issues/27 The culprit of the problem is in the asset’s URLs. I cannot decipher a file path by its URL. For instance, /assets/main.css?body=1 could be either app/assets/stylesheets/main.css, lib/assets/stylesheets/main.css or vendor/stylesheets/main.css. To fix

Hi, checking my package with check from devtools leads to the output Functions with \usage entries need to have the appropriate \alias entries, and all their arguments documented. The \usage entries must correspond to syntactically valid R code. See chapter ?Writing R documentation files? in the ?Writing R Extensions? manual. * checking Rd contents ... OK * checking for unstated dependencies in

has probado con: install_github('paquete",username='usuario')? 2013/12/20 Jose Luis Cañadas Reche <canadasreche en gmail.com>: > Hola a todos. > > Estoy intentando instalar el paquete likert utilizando devtools y obtengo el > siguiente error > > library(devtools) > install_github('likert','jbryer') > Installing github repo(s)

Hola, En GitHub estará siempre la última versión, pero también está el paquete en CRAN y puedes instalártelo como cualquier otro paquete ahí disponible... Saludos, Carlos Ortega www.qualityexcellence.es El 20 de diciembre de 2013, 14:54, José Luis Cañadas <canadasreche@gmail.com > escribió: > Si. Pero no funciona. En ordenador curro si funciona y tb tiene linux. > Seguiré

Gracias Oscar. Funciona perfectamente. Ya investigaré más adelante porque no funciona install_github Saludos y feliza navidad.. El 20/12/13 23:05, Oscar Perpiñan escribió: > tmp <- paste0(tempdir(), '/likert.zip') > download.file('https://github.com/jbryer/likert/archive/master.zip', > destfile=tmp, method='wget') > unzip(tmp,

Yo también tuve un problema parecido, en el momento que extrae el zip. Lo solucione como viene aquí: http://stackoverflow.com/questions/20408250/default-options-setting-for-unzip Saludos El 21 de diciembre de 2013, 9:00, Jose Luis Cañadas Reche < canadasreche@gmail.com> escribió: > Gracias Oscar. > > Funciona perfectamente. > Ya investigaré más adelante porque no funciona

I've already installed devtools-1.1 from Tru Huynh. http://people.centos.org/tru/devtools-1.1/ Thank You Tru. gcc 4.7.2 is so much newer than stock 4.4.7. (much better C++11 support) Why is devtools-1.1 not officially part of CentOS SCL? I know devtools-2.0 still has issues but 1.1 would bring us on par with Debian 7.0. http://wiki.centos.org/AdditionalResources/Repositories/SCL

Hi! I want to make the default environment for users the environment of devtoolset .. and i am thinking to do it this way: 1. make /bin/bash-devtools with the content scl enable devtoolset-2 bash "$@" 2. change for the prospective users the shell from /bin/bash to /bin/bash-devtoolset Is this the best way? Do anyone see or know of any pitfalls with this? Thanks a lot! Adrian

Hello, Please try this: > library(devtools) > create("mdaa") > setwd("mdaa") > dev_mode() d> install() Produces ...* DONE (mdaa) Reloading installed mdaa But when I then try to build documentation d> document() devtools/roxygen just hangs with a "?" like so: Updating mdaa documentation Loading mdaa ? I know this scenario is strange as

A mi no me dio problemas. Intenta instalar nuevamente RCurl. > library(devtools) > install_github('likert','jbryer') Installing github repo likert/master from jbryer Downloading likert.zip from https://github.com/jbryer/likert/archive/master.zip Installing package from /tmp/RtmpJuHsLY/likert.zip arguments 'minimized' and 'invisible' are for Windows only

This question was posed on SO : https://stackoverflow.com/questions/58118495/passing-extra-argumenets-to-devtoolsbuild but there has been no useful reply. Something seems to have changed in the |devtools|package, so that the following commands, that used to run now give an error I can't decipher: |>Sys.setenv(R_GSCMD="C:/Program

Hola, Puedes hacerlo sin devtools. Descargas el ZIP del repositorio, lo descomprimes, instalas el paquete que hay en CRAN para tener todas las dependencias instaladas y finalmente instalas el paquete en la versión de GitHub. tmp <- paste0(tempdir(), '/likert.zip') download.file('https://github.com/jbryer/likert/archive/master.zip', destfile=tmp,