> Martin Morgan
> on Tue, 25 Sep 2012 05:34:12 -0700 writes:
> On 09/25/2012 05:26 AM, Martin Maechler wrote:
>>
>>> Seemed like a good idea at the time,
>>
>> I'm curious. Why is it (setting max.print much too
>> large) a good idea?
> I usually set it
On 09/25/2012 05:26 AM, Martin Maechler wrote:
Seemed like a good idea at the time,
I'm curious. Why is it (setting max.print much too large)
a good idea?
I usually set it considerably smaller (50) than default to conserve
screen real estate, but then occasionally need to see more than my
> Seemed like a good idea at the time,
I'm curious. Why is it (setting max.print much too large)
a good idea?
> but
> > options(max.print = .Machine$integer.max)
> > 1:10
> [1]
> Program received signal SIGSEGV, Segmentation fault.
> because of an integer overflow at src/main/p
Seemed like a good idea at the time, but
> options(max.print = .Machine$integer.max)
> 1:10
[1]
Program received signal SIGSEGV, Segmentation fault.
because of an integer overflow at src/main/printvector.c:176
> sessionInfo()
R Under development (unstable) (2012-09-24 r60800)
Platf
