I was wondering if anyone knew of a good way to get R or ESS to stop executing the rest of the code beyond the point at which an error occurs if I am evaluating a region or buffer (I've only found the opposite request in the help archives). I was looking in the R help files but option(error=stop)
will only stop execution of the offending function or statement but not those that follow it. Thanks!
相关问题
- Symbol's function definition is void: declare-
- R - Quantstart: Testing Strategy on Multiple Equit
- Using predict with svyglm
- Reshape matrix by rows
- Extract P-Values from Dunnett Test into a Table by
相关文章
- How to convert summary output to a data frame?
- How to plot smoother curves in R
- Paste all possible diagonals of an n*n matrix or d
- ess-rdired: I get this error “no ESS process is as
- How to use doMC under Windows or alternative paral
- dyLimit for limited time in Dygraphs
- Saving state of Shiny app to be restored later
- How to insert pictures into each individual bar in
According to the ESS manual, this should work:
C-c C-c
(comint-interrupt-subjob) Sends aControl-C
signal to the ESS process. This has the effect of aborting the current command.John Fox has a website where he offers a configuration for ESS. In it, he has this function:
You should be able to add this function to the menu in XEmacs using:
You might check out the rest of his configuration file and documentation to see if it interests you. I haven't tried this yet, but I hope that it works for you!
Charlie
If R/ESS is hogging up so much compute time that your emacs/ESS is unresponsive to C-c C-c, you can also save it by sending an INTERRUPT signal from the terminal.
First: figure out R's processID using
top
orps
. (mine was 98490 Then:kill -2 98490
That sends an interrupt signal and you get your ESS/Emacs and R session back?break
Only gets you out of loop.
?try
Lets you set up code that might fail and gracefully recover.