search for: norstudiogd

...RStudio, you >> get an RStudio device, not the standard device for the platform because >> it overrides the device option. So I've had to have the library do >> platform detection and platform-specific device calls, which R CMD check >> doesn't like. I believe that noRStudioGD argument was avoided to give >> users a way around this, but it doesn't seem to be behaving correctly in >> the unix interactive case. > > It seems like the best workaround here could come from RStudio. They > could provide a way for a user to indicate that they sometimes...

...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. So I've had to have the library do platform detection and platform-specific device calls, which R CMD check doesn't like. I believe that noRStudioGD argument was avoided to give users a way around this, but it doesn't seem to be behaving correctly in the unix interactive case. On 09/25/2015 08:31 PM, Ott Toomet wrote: > Can you describe your problem a bit more? > > * What kind of unix system do you have?? > * Can you run othe...

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 and R_INTERACIVE_DEVICE not set). Do other unix RStudio users see this beha...

...;>> get an RStudio device, not the standard device for the platform because >>> it overrides the device option. So I've had to have the library do >>> platform detection and platform-specific device calls, which R CMD check >>> doesn't like. I believe that noRStudioGD argument was avoided to give >>> users a way around this, but it doesn't seem to be behaving correctly in >>> the unix interactive case. >> >> It seems like the best workaround here could come from RStudio. They >> could provide a way for a user to indicate...

...when using RStudio, you > get an RStudio device, not the standard device for the platform because > it overrides the device option. So I've had to have the library do > platform detection and platform-specific device calls, which R CMD check > doesn't like. I believe that noRStudioGD argument was avoided to give > users a way around this, but it doesn't seem to be behaving correctly in > the unix interactive case. It seems like the best workaround here could come from RStudio. They could provide a way for a user to indicate that they sometimes don't want to us...

> The problem is that the device chosen by dev.new() depends on the GUI. > You can see the code that does this in grDevices:::.onLoad. So in fact > with noRstudioGD=TRUE, the decision is identical to what it is in R: > you only get X11 if your GUI is X11 or Tk, you get pdf otherwise. > It's pretty common to use R on a machine where X11 won't work, so this > makes sense. But not if running from RStudio always causes the X11 check to fail. If...

...ce. 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, 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 and R_INTERACIVE_DEVICE not set). > > Do other unix RStudio...