Commit c734ae59 authored by Richard M. Stallman's avatar Richard M. Stallman
Browse files

(Timers): Update previous change.

parent b437860a
2004-12-31 Richard M. Stallman <rms@gnu.org>
* os.texi (Timers): Update previous change.
2004-12-30 Kim F. Storm <storm@cua.dk> 2004-12-30 Kim F. Storm <storm@cua.dk>
* display.texi (Line Height): Total line-height is now specified * display.texi (Line Height): Total line-height is now specified
......
...@@ -1368,10 +1368,10 @@ because most timer functions don't do a lot of work. Indeed, for a ...@@ -1368,10 +1368,10 @@ 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 timer to call a function that takes substantial time to run is likely
to be annoying. to be annoying.
Timer functions should normally not alter the current buffer It is usually a bad idea for timer functions to alter buffer
contents, but it may be ok to alter some other buffer that exists for contents. When they do, they usually should call @code{undo-boundary}
special purposes. A general guideline is that if a buffer has undo both before and after changing the buffer, to separate the timer's
enabled, timers should not write in it. changes from user commands' changes.
@deffn Command run-at-time time repeat function &rest args @deffn Command run-at-time time repeat function &rest args
This sets up a timer that calls the function @var{function} with This sets up a timer that calls the function @var{function} with
...@@ -1486,11 +1486,6 @@ minutes, and even if there have been garbage collections and autosaves. ...@@ -1486,11 +1486,6 @@ minutes, and even if there have been garbage collections and autosaves.
input. Then it becomes idle again, and all the idle timers that are input. Then it becomes idle again, and all the idle timers that are
set up to repeat will subsequently run another time, one by one. set up to repeat will subsequently run another time, one by one.
It is legitimate for an idle timer to edit the current buffer. If
it does, it should explicitly call @code{undo-boundary} once at the
beginning and once just before exiting, since Emacs won't do that
automatically for an idle timer.
@defun cancel-timer timer @defun cancel-timer timer
Cancel the requested action for @var{timer}, which should be a value Cancel the requested action for @var{timer}, which should be a value
previously returned by @code{run-at-time} or @code{run-with-idle-timer}. previously returned by @code{run-at-time} or @code{run-with-idle-timer}.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment