Mercurial > emacs
changeset 73117:43aadb7f2e64
* os.texi (Timers): Mention with-local-quit.
| author | Chong Yidong <cyd@stupidchicken.com> |
|---|---|
| date | Mon, 25 Sep 2006 15:20:44 +0000 |
| parents | febee7739295 |
| children | c272319e5fcc |
| files | lispref/ChangeLog lispref/os.texi |
| diffstat | 2 files changed, 10 insertions(+), 1 deletions(-) [+] |
line wrap: on
line diff
--- a/lispref/ChangeLog Mon Sep 25 15:13:07 2006 +0000 +++ b/lispref/ChangeLog Mon Sep 25 15:20:44 2006 +0000 @@ -1,3 +1,7 @@ +2006-09-25 Chong Yidong <cyd@stupidchicken.com> + + * os.texi (Timers): Mention with-local-quit. + 2006-09-24 Richard Stallman <rms@gnu.org> * searching.texi (Searching and Matching): Mention property search.
--- a/lispref/os.texi Mon Sep 25 15:13:07 2006 +0000 +++ b/lispref/os.texi Mon Sep 25 15:20:44 2006 +0000 @@ -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 +@code{with-local-quit}, 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}