I tried CRAN R again, and could NOT reproduce this error, at least not this
time. Maybe I inadvertently used my own compiled version last time I tried CRAN
R. I may try the folks at homebrew to trace this issue. Thank you so much to
everybody who chimed in.
Cheers,
Martin
On 28 Jan 2012, a
Martin,
On Jan 28, 2012, at 9:31 PM, Simon Urbanek wrote:
>
> On Jan 28, 2012, at 8:21 PM, Martin Renner wrote:
>
>> Thank you to everybody who replied! Simon, on my machine, I can reproduce
>> this segfault every time using these steps:
>>
>> - open Terminal.app (or iTerm or Aquamacs), start
On Jan 28, 2012, at 8:21 PM, Martin Renner wrote:
> Thank you to everybody who replied! Simon, on my machine, I can reproduce
> this segfault every time using these steps:
>
> - open Terminal.app (or iTerm or Aquamacs), start R --vanilla (RStudio, or
> R.app)
> in R:
> - x11() (in Term
Thank you to everybody who replied! Simon, on my machine, I can reproduce this
segfault every time using these steps:
- open Terminal.app (or iTerm or Aquamacs), start R --vanilla (RStudio, or
R.app)
in R:
- x11() (in Terminal, my R defaults to x11, without me doing anything; in
R.app
Dear Simon,
Thank you for your replies, I understand now your explanation about R.app.
I do not think that the topic on the locale is unrelated to the plot
problem, since adding to .bashrc:
export LC_CTYPE=en_US.UTF-8
export LC_ALL=en_US.UTF-8
does solve the problem with plot(), as you can
On Jan 28, 2012, at 1:46 PM, cstrato wrote:
> Yes, although I have started X11.app and run R from within an xterm I get:
>
> > plot(1:8)
> No protocol specified
> Error in X11(d$display, d$width, d$height, d$pointsize, d$gamma, d$colortype,
> :
> unable to start device X11
> In addition: Warn
Here is one more confusing issue:
I know that sessionInfo() gives
locale:
[1] C
This was the case when starting R64.app or starting R from the command
line. Following the advice from an earlier topic I did on the command line:
$ defaults write org.R-project.R force.LANG en_US.UTF-8
Since star
Martin,
can you specify more precisely what you're doing? Issuing the code you sent
would use Quartz, so apparently you're doing other things that you didn't
mention - so can you share those so we can try to reproduce it?
Thanks,
Simon
On Jan 27, 2012, at 7:17 PM, Martin Renner wrote:
> Hi A
Yes, although I have started X11.app and run R from within an xterm I get:
> plot(1:8)
No protocol specified
Error in X11(d$display, d$width, d$height, d$pointsize, d$gamma,
d$colortype, :
unable to start device X11
In addition: Warning message:
In function (display = "", width, height, poin
For what it is worth I don't see this problem on Snow Leopard, self-compiled.
You can make quartz the default device by putting
Sys.setenv("R_INTERACTIVE_DEVICE" = "quartz")
in your .Rprofile.
Kasper
On Fri, Jan 27, 2012 at 7:17 PM, Martin Renner wrote:
> Hi All,
>
> Is anybody else experienci
Hi All,
Is anybody else experiencing problems with X11 and R under Mac OS X 10.7
(Lion)? If yes, maybe it's not specific to my machine. R segfaults when I try
to plot to a X11 device, e.g. open R in the terminal and calling
> plot (1:10)
(see below). Plotting to a quartz device works fine. I'
11 matches
Mail list logo