mirror of
git://git.sv.gnu.org/emacs.git
synced 2026-01-05 03:20:39 -08:00
* os.texi (Timers): Mention with-local-quit.
This commit is contained in:
parent
94019f61df
commit
2d56beeda6
2 changed files with 10 additions and 1 deletions
|
|
@ -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.
|
||||
|
|
|
|||
|
|
@ -1386,7 +1386,12 @@ function, because quitting out of many timer functions can leave
|
|||
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}
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue