[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Emacs-diffs] Changes to emacs/lispref/os.texi,v
From: |
Chong Yidong |
Subject: |
[Emacs-diffs] Changes to emacs/lispref/os.texi,v |
Date: |
Mon, 25 Sep 2006 15:20:44 +0000 |
CVSROOT: /sources/emacs
Module name: emacs
Changes by: Chong Yidong <cyd> 06/09/25 15:20:44
Index: os.texi
===================================================================
RCS file: /sources/emacs/emacs/lispref/os.texi,v
retrieving revision 1.95
retrieving revision 1.96
diff -u -b -r1.95 -r1.96
--- os.texi 21 Sep 2006 01:51:55 -0000 1.95
+++ os.texi 25 Sep 2006 15:20:44 -0000 1.96
@@ -1386,7 +1386,12 @@
things in an inconsistent state. This is normally unproblematical
because most timer functions don't do a lot of work. Indeed, for a
timer to call a function that takes substantial time to run is likely
-to be annoying.
+to be annoying. If a timer function needs to allow quitting, it
+should use @code{with-local-quit} (@pxref{Quitting}). For example, if
+a timer function calls @code{accept-process-output} to receive output
+from an external process, that call should be wrapped inside
address@hidden, to ensure that @kbd{C-g} works if the external
+process hangs.
It is usually a bad idea for timer functions to alter buffer
contents. When they do, they usually should call @code{undo-boundary}