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 small
setting (e.g., ls(getNamespace("Matrix"))) and don't want to guess at
how much I want to see.
Thanks for your fix.
Martin
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)
Platform: x86_64-unknown-linux-gnu (64-bit)
...
also R-patched, etc.
Thank you, Martin. I'm about to commit fixes for this.
"another" Martin.
Martin
--
Computational Biology / Fred Hutchinson Cancer Research Center
1100 Fairview Ave. N.
PO Box 19024 Seattle, WA 98109
--
Computational Biology / Fred Hutchinson Cancer Research Center
1100 Fairview Ave. N.
PO Box 19024 Seattle, WA 98109
Location: Arnold Building M1 B861
Phone: (206) 667-2793
______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
