On 10/02/2017 19:27, Prof Brian Ripley wrote:
Note that there are at least 5 separate png() devices, so Linux was not
using the (default) device used on Windows.
In general, the device-limits info is not on the help page because we do
not know it. On Windows the default device limits depend on
Note that there are at least 5 separate png() devices, so Linux was not
using the (default) device used on Windows.
In general, the device-limits info is not on the help page because we do
not know it. On Windows the default device limits depend on the OS
version, 32/64-bit, RAM and the graph
So do a number of other interactive programs when working in a
terminal (e.g. python) since it looks like your terminal is configured
for those two actions to send the SIGQUIT signal. Whether R should
ignore that signal, under some circumstances at least, is another
question.
Best,
luke
On Fri,
Control-backslash is the default way to generate SIGQUIT from the
keyboard on Unix and SIGQUIT, by default, aborts the process and
causes it to produce a core dump. Do you want R to catch SIGQUIT?
% stty --all
speed 38400 baud; rows 24; columns 64; line = 0;
intr = ^C; quit = ^\; erase = ^H; kill
When running R from the terminal on Linux (Ubuntu 16.04), it core
dumps whenever / wherever I press Ctrl-4 or Ctrl-\. You get thrown
back to the terminal with "Quit (core dump)" being the only message.
Grepping the R source code, it doesn't look like that message is
generated by R itself. Over on
Thanks Berend, I will make that change and submit to CRAN.
Best, Göran
On 2017-02-10 16:13, Berend Hasselman wrote:
On 10 Feb 2017, at 14:53, Göran Broström wrote:
Thanks to all who answered my third question. I learned something, but:
On 2017-02-09 17:44, Martin Maechler wrote:
On 9 F
Martin,
That was it- I forgot the "LinkingTo" line. I had read that section of the manual
twice in the last 2 days, yet somehow missed that critical line both times. And even
worse, the final sentence of said section references my own coxme package as an example of
how to do it correctly!
Were you suppressing warnings? I get a warning along with the "unable
to start device 'png'" in some cases where it fails. E.g., on Linux
> png("Figure1A.png", h = 7, w = 7, res = 1e5, units = "cm")
Error in png("Figure1A.png", h = 7, w = 7, res = 1e+05, units = "cm") :
unable to start device
> Dario Strbenac
> on Fri, 10 Feb 2017 02:00:08 + writes:
> Good day,
> Could the documentation of graphics devices give some explanation of how
big the bitmap limits are? For example,
>> png("Figure1A.png", h = 7, w = 7, res = 1000, units = "cm")
> Results in E
> Therneau, Terry M , Ph D
> on Thu, 9 Feb 2017 12:56:17 -0600 writes:
> Martyn,
> No, that didn't work.
> One other thing in the mix (which I don't think is the issue) is that I
call one of the
> C-entry points of expm. So the DESCRIPTION file imports expm, the
NA
> On 10 Feb 2017, at 14:53, Göran Broström wrote:
>
> Thanks to all who answered my third question. I learned something, but:
>
> On 2017-02-09 17:44, Martin Maechler wrote:
>>
On 9 Feb 2017, at 16:00, Göran Broström wrote:
In my package 'glmmML' I'm using old C code and linpa
Thanks to all who answered my third question. I learned something, but:
On 2017-02-09 17:44, Martin Maechler wrote:
On 9 Feb 2017, at 16:00, Göran Broström wrote:
In my package 'glmmML' I'm using old C code and linpack in the optimizing
procedure. Specifically, one part of the code looks li
12 matches
Mail list logo
