Prof Brian Ripley wrote:
> Do you have DISPLAY set pointing to an X11 server you do not have
> access to? It seems so. The solution is to set your X11 settings
> properly.
>
> This is coming from Xlib (XOpenDisplay, I believe) and so is not an R
> error or warning, and is not output on an R c
Do you have DISPLAY set pointing to an X11 server you do not have
access to? It seems so. The solution is to set your X11 settings
properly.
This is coming from Xlib (XOpenDisplay, I believe) and so is not an R
error or warning, and is not output on an R connection but on a C file.
On Mon,
No; I've tried/do that too.
/Henrik
Roger D. Peng wrote:
> Would using 'capture.output()' work for you in this case?
>
> -roger
>
> Henrik Bengtsson wrote:
>
>>Just for the record (not a request for fix) and an ad hoc workaround if
>>anyone needs it:
>>
>>REASON:
>>Running an R script as a pl
Would using 'capture.output()' work for you in this case?
-roger
Henrik Bengtsson wrote:
> Just for the record (not a request for fix) and an ad hoc workaround if
> anyone needs it:
>
> REASON:
> Running an R script as a plugin on a remote Suse Linux 8.2 with R v2.1.0
> (2005-04-18), I have no
Just for the record (not a request for fix) and an ad hoc workaround if
anyone needs it:
REASON:
Running an R script as a plugin on a remote Suse Linux 8.2 with R v2.1.0
(2005-04-18), I have noticed that capabilities() generates (to standard
error)
Xlib: connection to "base:0.0" refused by
