similar to: declaring nonS3method

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() when using RStudio, you get an RStudio device, not the standard device for the platform because it overrides the device option.

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() when using RStudio, you > get an RStudio device, not the

And my non-cross-posted cross-posting: "Dear Martin, Thank you for addressing this issue. Introducing a nonS3method() directive in NAMESPACE seems a reasonable solution. It could replace export() for functions with "."s in their names. Best, John" On Fri, 12 Jun 2015 10:12:07 +0200 Martin Maechler <maechler at stat.math.ethz.ch> wrote: > This is a topic '

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

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

On 12/06/2015 4:12 AM, Martin Maechler wrote: > This is a topic ' "apparent S3 methods" note in R CMD check ' > from R-package-devel > https://stat.ethz.ch/pipermail/r-package-devel/2015q2/000126.html > > which is relevant to here because some of us have been thinking > about extending R because of the issue. > > John Fox, maintainer of the

On 12/06/2015 7:16 AM, Kurt Hornik wrote: >>>>>> Duncan Murdoch writes: > >> On 12/06/2015 4:12 AM, Martin Maechler wrote: >>> This is a topic ' "apparent S3 methods" note in R CMD check ' >>> from R-package-devel >>> https://stat.ethz.ch/pipermail/r-package-devel/2015q2/000126.html >>> >>> which is

To me, it seems like there's actually two problems here: 1) Preventing all() from dispatching to all.effects() for objects of class effects 2) Eliminating the NOTE in R CMD check My impression is that 1) actually causes few problems, particularly since people are mostly now aware of the problem and avoid using `.` in function names unless they're S3 methods. Fixing this issue seems like

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

Can you describe your problem a bit more? * What kind of unix system do you have? * Can you run other X11 programs? 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

The notes available off the devloper page https://developer.r-project.org/ describe some of the rationale for the S3 method search design. One thing that has changed since then is that all packages now have name spaces. We could change the search algorithm to skip attached package exports (and package imports and base), which would require methods defined in packages that are to be accessible

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

>>>>> Duncan Murdoch writes: > On 12/06/2015 4:12 AM, Martin Maechler wrote: >> This is a topic ' "apparent S3 methods" note in R CMD check ' >> from R-package-devel >> https://stat.ethz.ch/pipermail/r-package-devel/2015q2/000126.html >> >> which is relevant to here because some of us have been thinking >> about extending

This is a topic ' "apparent S3 methods" note in R CMD check ' from R-package-devel https://stat.ethz.ch/pipermail/r-package-devel/2015q2/000126.html which is relevant to here because some of us have been thinking about extending R because of the issue. John Fox, maintainer of the 'effects' package has enquired about the following output from 'R CMD check

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

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

>>>>> Luke Tierney <luke-tierney at uiowa.edu> >>>>> on Fri, 12 Jun 2015 10:30:29 -0500 writes: > The notes available off the devloper page > https://developer.r-project.org/ describe some of the rationale for > the S3 method search design. One thing that has changed since then is > that all packages now have name spaces. We

>>>>> Duncan Murdoch writes: > On 12/06/2015 7:16 AM, Kurt Hornik wrote: >>>>>>> Duncan Murdoch writes: >> >>> On 12/06/2015 4:12 AM, Martin Maechler wrote: >>>> This is a topic ' "apparent S3 methods" note in R CMD check ' >>>> from R-package-devel >>>>

On 12/06/2015 10:53 AM, Hadley Wickham wrote: > To me, it seems like there's actually two problems here: > > 1) Preventing all() from dispatching to all.effects() for objects of > class effects > 2) Eliminating the NOTE in R CMD check > > My impression is that 1) actually causes few problems, particularly > since people are mostly now aware of the problem and avoid

On 29/09/2015 2:00 PM, Skye Bender-deMoll wrote: > > > 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