Interruption of a running job

Rich Heiberger rmh at
Tue May 16 19:25:35 CEST 2000

I agree that it is unfortunate that the Windows version of S-Plus
does not behave the same as the Unix version.

If I read you correctly, you are killing the entire buffer, not just
the executable program in Sqpe.  If you just kill the job, and leave
the buffer active, then you will not have to regenerate the output.
You can do this with the Signals/QUIT or Signals/KILL menu.
Then you can restart S-Plus with another M-x Sqpe+4 in the same buffer.

Other strategies you could use include using the sink() command to put
the output in a file.  Then it won't clutter your screen, it will
appear to execute faster because you don't have to wait for the output
to be displayed on the screen, and you will be able to study it (or
edit it) later.  If you are running bash, you can get see it as it
happens with sink() by using tail -f.

1. In a *shell* buffer (running bash, not MSDOS), enter
        tail -f myoutput.file
2. split the screen and in the *S+4* buffer (running M-x Sqpe+4)
        1:3000   ## or some useful command

The output will appear in the *shell* buffer as it is created.
The *S+4* buffer will be small.  You can kill the tail process and
not hurt the S+4 process or the output file.

ess-help mailing list -- To (un)subscribe, send
subscribe	or	unsubscribe
(in the "body", not the subject !)  To: ess-help-request at

More information about the ESS-help mailing list