search for: onintr

...stephen pope scp at predict.com Here's the patch. build_main at mambo:/vobs/products/R> gdiff -ub src/unix/sys-std.c@@/main/3 src/unix/sys-std.c --- src/unix/sys-std.c@@/main/3 Thu Jan 12 11:39:55 2006 +++ src/unix/sys-std.c Fri Mar 31 23:12:16 2006 @@ -294,13 +294,13 @@ else onintr(); } - tv.tv_sec = 0; - tv.tv_usec = usec; + tv.tv_sec = usec/1000000; + tv.tv_usec = usec % 1000000; maxfd = setSelectMask(R_InputHandlers, &readMask); if (ignore_stdin) FD_CLR(fileno(stdin), &readMask); if (R_SelectEx(maxfd+1, &readMask, N...

...preprocessing directive HAVE_AQUA, which could explain why Spencer observes a different behavior than Peter and Berend (all on macOS). Whenever the R_CheckUserInterrupt() function is called it in turn always calls R_ProcessEvents(). At the end, there is a code snippet - if (R_interrupts_pending) onintr(); - which is Windows specific and could be another important difference between Windows and Unix. This function is defined in: * src/main/errors.c (https://github.com/wch/r-source/blob/trunk/src/main/errors.c#L114-L134) The do_setTimeLimit() function controls global variables cpuLimitValue and...

...in why Spencer >> observes a different behavior than Peter and Berend (all on macOS). >> >> >> Whenever the R_CheckUserInterrupt() function is called it in turn >> always calls R_ProcessEvents(). At the end, there is a code snippet - >> if (R_interrupts_pending) onintr(); - which is Windows specific and >> could be another important difference between Windows and Unix. This >> function is defined in: >> >> * src/main/errors.c >> (https://github.com/wch/r-source/blob/trunk/src/main/errors.c#L114-L134) >> >> >> The d...

A non-text attachment was scrubbed... Name: not available Type: text Size: 1287 bytes Desc: not available Url : https://stat.ethz.ch/pipermail/r-help/attachments/19980406/39dc7891/attachment.pl

A non-text attachment was scrubbed... Name: not available Type: text Size: 668 bytes Desc: not available Url : https://stat.ethz.ch/pipermail/r-help/attachments/19980514/af07cf17/attachment.pl

list(...), I am looking for a way to interrupt R from a callback: specifically, to interrupt plotting (typically on a cairoDevice, but would be good if it worked with other devices too). Of course, one can interrupt R nicely from the console with Ctrl-C (or Esc in Rgui), but I need to do it from a GUI. Callbacks run in a new thread, so obviously stop() etc will not work. I tried to look into how

...QUA, which could explain why Spencer > observes a different behavior than Peter and Berend (all on macOS). > > > Whenever the R_CheckUserInterrupt() function is called it in turn > always calls R_ProcessEvents(). At the end, there is a code snippet - > if (R_interrupts_pending) onintr(); - which is Windows specific and > could be another important difference between Windows and Unix. This > function is defined in: > > * src/main/errors.c > (https://github.com/wch/r-source/blob/trunk/src/main/errors.c#L114-L134) > > > The do_setTimeLimit() function con...

...rent behavior than Peter and Berend (all on macOS). >>>> >>>> >>>> Whenever the R_CheckUserInterrupt() function is called it in turn >>>> always calls R_ProcessEvents(). At the end, there is a code snippet - >>>> if (R_interrupts_pending) onintr(); - which is Windows specific and >>>> could be another important difference between Windows and Unix. This >>>> function is defined in: >>>> >>>> * src/main/errors.c >>>> (https://github.com/wch/r-source/blob/trunk/src/main/errors.c#L11...

...gt; observes a different behavior than Peter and Berend (all on macOS). >>> >>> >>> Whenever the R_CheckUserInterrupt() function is called it in turn >>> always calls R_ProcessEvents(). At the end, there is a code snippet - >>> if (R_interrupts_pending) onintr(); - which is Windows specific and >>> could be another important difference between Windows and Unix. This >>> function is defined in: >>> >>> * src/main/errors.c >>> (https://github.com/wch/r-source/blob/trunk/src/main/errors.c#L114-L134) >>>...

setTimeLimit(elapsed=1) causes a timeout error whenever a call takes more than one second. For instance, this is how it works on Windows (R 3.3.1): > setTimeLimit(elapsed=1) > Sys.sleep(10); message("done") Error in Sys.sleep(10) : reached elapsed time limit Also, the error propagates immediately and causes an interrupt after ~1 second; > system.time({ Sys.sleep(10);