Re: [Rd] [FORGED] Different results based on the order of arguments to par

2016-03-14 Thread Paul Murrell
Hi I'm going to try to blame user error here. par(usr) is used to reset the coordinates on the CURRENT plot. par(plt) is used to specify the location of the NEXT plot. The correct approach should be to set up the location for the next plot, start a new plot, set up coordinates on the new plot

Re: [Rd] Help with libiconv problem

2016-03-14 Thread Mick Jordan
On 3/14/16 1:49 PM, Mick Jordan wrote: A couple of my colleagues are having problems building R-3.2.4 on Mac OS X El Capitan somehow related to libiconv. I personally don't have any problems on either of my Macs. I'm hoping thie make log might trigger something in the readers of this list: gc

[Rd] Different results based on the order of arguments to par

2016-03-14 Thread Greg Snow
I ran into this issue when trying to modify a subplot (subplot function in the TeachingDemos package), but here is a more minimal example of the issue (I don't know that it is serious enough to call a bug): This code works how I expect: dev.new() hist(rexp(100)) par(plt=c(0.5,0.9,0.5,0.77), usr=

[Rd] Help with libiconv problem

2016-03-14 Thread Mick Jordan
A couple of my colleagues are having problems building R-3.2.4 on Mac OS X El Capitan somehow related to libiconv. I personally don't have any problems on either of my Macs. I'm hoping thie make log might trigger something in the readers of this list: gcc -dynamiclib -Wl,-headerpad_max_install