search for: skyeom

...that the computer was not set > up to support X11.? As a minimum, you have to install /xauth/, and > potentially also other libraries if you want to install packages from > source. > > Best, > Ott > > On Fri, Sep 25, 2015 at 11:53 AM, Skye Bender-deMoll > <skyebend at skyeome.net <mailto:skyebend at skyeome.net>> wrote: > > Hi R-devl, > > I'm still unable to force opening an *interactive* non-Rstudio > platform-specific plot device on *unix* systems. > > dev.new() add a new argument 'noRStudioGD' in R 3.1.1.? T...

Hi R-devl, I'm still unable to force opening an *interactive* non-Rstudio platform-specific plot device on *unix* systems. dev.new() add a new argument 'noRStudioGD' in R 3.1.1. Thank you. It works for me when using RStudio on Windows, but on the unix system it opens a pdf device instead of an interactive device when using an interactive RStudio session (with R_DEFAULT_DEVICE

Dear R-devel I have a function in a package that essentially provides a wrapper for a group of functions in another Suggested package (it sets appropriate defaults for the context, transforms output, etc). I've implemented this by verifying that the package was loaded with require(sna) and then do.call(snaFunName, args = args) The rDevel check is requesting that I use

...t; up to support X11.? As a minimum, you have to install /xauth/, and >> potentially also other libraries if you want to install packages from >> source. >> >> Best, >> Ott >> >> On Fri, Sep 25, 2015 at 11:53 AM, Skye Bender-deMoll >> <skyebend at skyeome.net <mailto:skyebend at skyeome.net>> wrote: >> >> Hi R-devl, >> >> I'm still unable to force opening an *interactive* non-Rstudio >> platform-specific plot device on *unix* systems. >> >> dev.new() add a new argument 'noRS...

do.call(sna::snaFunName, args = args) ? Hadley On Tue, Feb 24, 2015 at 1:29 PM, Skye Bender-deMoll <skyebend at skyeome.net> wrote: > Dear R-devel > > I have a function in a package that essentially provides a wrapper for a > group of functions in another Suggested package (it sets appropriate > defaults for the context, transforms output, etc). I've implemented this by > verifying that th...

...I had a similar issue, and the problem was that the computer was not set up to support X11. As a minimum, you have to install /xauth/, and potentially also other libraries if you want to install packages from source. Best, Ott On Fri, Sep 25, 2015 at 11:53 AM, Skye Bender-deMoll <skyebend at skyeome.net> wrote: > Hi R-devl, > > I'm still unable to force opening an *interactive* non-Rstudio > platform-specific plot device on *unix* systems. > > dev.new() add a new argument 'noRStudioGD' in R 3.1.1. Thank you. It > works for me when using RStudio on Windows...

Dear R-devel, Recent versions of R CMD check have been flagging apparent S3 methods that are not registered in the NAMESPACE as such. In most situations this is very helpful. However, I have few cases in existing packages where we have unfortunately named functions using a "." in them that makes them appear as S3 methods when they are not. As there is no existing class

Dear R-developers, As part of our package building process, we maintain internal CRAN-like repositories of our packages. This has worked pretty well, but we are running into issues with R 3.1 and OSX mavericks. Specifically, machines with osx mavericks seem to, by default, expect packages to be located under a 'mavericks' sub-directory, but this is not the location reported when

Dear R-devs, I'm working on a package where we have a function that modifies an Object via .Call to a C function. Unfortunately in some situations this counterintuitive modifies a previously made copy of the object passed to the function. For example, if I first make an assignment to "copy" the object, b<-a and then modify 'a' , the value of 'b' will be

If Martin's proposal for declaring non-S3 methods in NAMESPACE is feasible, it would be very helpful. The packages we support have multiple examples of unfortunately named functions non-S3 functions, so creating a route for migrating them into compliance would be great. best, -skye On 06/12/2015 03:00 AM, r-package-devel-request at r-project.org wrote: > Message: 11 > Date: Fri,

Dear R-devel, I have a class 'myClass' in R that is essentially a list with pre-specified structure. It has an assignment operator which is going to do some things and then should assign the value using the regular list assignment operator `$<-.myClass`<-function(x,i,value){ # do some pre-processing stuff # make the assignment using the default list assignment

Dear R devel, What is the correct way to write package tests that could possibly fail due to locale collation behavior? Is it safe/proper for me to call Sys.setlocale("LC_COLLATE", "en_US.UTF-8") in each test file? Or should I explicitly force collation to C before writing tests? Or do I need to always call sort() on my comparison objects to ensure they are sorted in

Dear R-sig-debian, As of last night, we are running into a build failure when trying to compile the development version of R from the svn repository, Revision: 64090: ./configure && make -j4 distclean && ./configure && make -j4 [lots of normal compile output not shown...] building/updating vignettes for package 'utils' ... processing 'Sweave.Rnw' Error:

Hi Folks, I've recently transitioned to Debian 8.0 and was having a hard time getting Rmpi to work. I believed I'd successfully installed dependencies via > sudo apt-get install r-cran-rmpi > apt-show-versions r-cran-rmpi r-cran-rmpi:amd64/jessie 0.6-5-1 uptodate but when installing the package I was still getting checking mpi.h presence... no checking for mpi.h... no

Dear R-Devel, Note: I posted a similar message to R-sig-debian yesterday because I assumed it was a Debian issue, received response that it it may be more appropriate for r-devel since it involves building from the svn version. As of Oct 21, we are running into a build failure when trying to compile the development version of R from the svn repository. The problem still persists as of

Dear r-devel-opers, I'm working on a package that does some plot-intensive work using the animation library. It turns out that this performs very badly in the RStudio plot device, which is the preferred IDE for our team. Our kludgy solution is to detect if the Rstudio device is running, and if so, open another plot device to do the rendering and close it when done:

Dear R-devel, Question: How can I get Sweave to recognize that the \thebibliography section is already created and generate the vignette pdf with a single pass? Or is there a way to let R CMD build know that Sweave needs to be run twice? If (1) is not possible, any suggestions how to auto-generate a crude generic bibtex .bib file from my existing document? Background: I maintain

Dear R devel, Is libcurl support required to run R.devel, or is it optional? I'm compiling R.devel on an older Debian machine that only has libcurl version 7.21.0 The R news file says " Sun, 25 Jan 2015 CHANGES IN R-devel NEW FEATURES Optional use of ?libcurl? (version 7.28.0 from Oct 2012 or later) for Internet access (including on Windows): ... CHANGES IN R-devel

On 09/26/2015 03:22 AM, Duncan Murdoch wrote: > On 26/09/2015 1:42 AM, Skye Bender-deMoll wrote: >> Sorry, should have given more background. x11 works fine on all my >> systems when called by x11(). I'm the maintainer of a package that uses >> the animation library, which has performance issues when used with the >> RStudio plot device. But if you call plot.new()