Hi, there is a minor glitch with Ctrl-C on Windows:
1. Start Rterm.exe 2. Press Ctrl-C (without ENTER afterwards) to generate a user interrupt signal. 3. Type Sys.sleep(1e6) + ENTER. 4. The user interrupt in Step 2 causes Sys.sleep() in Step 3 to be interrupted. I can reproduce this behavior on Windows 7 64-bit and 'Rterm.exe' with R v2.13.0 (2011-04-13), v2.15.0 Patched (2012-05-26 r59447), and Devel (2012-06-20 r59586). It occurs neither with 'R' on OSX and R v2.15.0 (2012-03-30) nor with 'R' on Linux and R v2.15.0 Patched (2012-05-01 r59304). In those cases, pressing Ctrl-C also advances the prompt (just as if Ctrl-C was followed by an ENTER). This is not the case with Rterm on Windows, where pressing Ctrl-C does not advance the prompt. However, pressing Ctrl-C and then ENTER, gives an empty line between the two prompts (just as if Ctrl-C was followed by an ENTER that "didn't get through"). /Henrik PS. I am aware of the recent Bug/Fix #14948 [https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=14948]. ______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
