|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
From: amgreene@ATHENA.MIT.EDU Date: Tue, 5 Feb 91 10:17:29 -0500 To: qjb@ATHENA.MIT.EDU, bugs@ATHENA.MIT.EDU Isn't this emacs' standard way of dealing? From P. 229 of the GNU Emacs Manual: 29.2.5 Emergency Escape Because at times there have been bugs causing Emacs to loop without checking quit-flag, as special feature causes Emacs to be suspended immediately if you type a second C-g while the flag is already set, so you can always get out of GNU Emacs. Normally Emacs recognizes and clears quit-flag (and quits!) quickly enough to prevent this from hapenning. When you resume Emacs after a suspension caused by multiple C-g, it asks two questions before going back to what it had been doing: Auto-save? (y or n) Abort (and dump core)? (y or n) Answer each one with y or n followed by RET. .... If Emacs is not really hung, just slow, you may invoke the double C-g feature without meaning to. Then just resume an answer n to both questions, and you will arrive at your former state. Presumably the quit you requested will happen soon. The double-C-g feature may be turned off when Emacs is running under a window system, since the window system always enables you to kill Emacs....
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |