summaryrefslogtreecommitdiff
path: root/lispref
diff options
context:
space:
mode:
authorRichard M. Stallman <rms@gnu.org>2002-04-07 18:58:06 +0000
committerRichard M. Stallman <rms@gnu.org>2002-04-07 18:58:06 +0000
commit8a56d8ed331be880a2f7be05b15886bd7acb269d (patch)
tree584ffbdd4aff77347e6e0d7342cf71e07258573d /lispref
parent39296e3af82fef4a3d06b2b3e91bacd46a0593d8 (diff)
downloademacs-8a56d8ed331be880a2f7be05b15886bd7acb269d.tar.gz
Explain that sentinels cannot run recursively.
Diffstat (limited to 'lispref')
-rw-r--r--lispref/processes.texi5
1 files changed, 5 insertions, 0 deletions
diff --git a/lispref/processes.texi b/lispref/processes.texi
index 81023719429..0b5786f2cd8 100644
--- a/lispref/processes.texi
+++ b/lispref/processes.texi
@@ -1297,6 +1297,11 @@ programs was running when the sentinel was started. However, if
off. This makes it possible to use the Lisp debugger to debug the
sentinel. @xref{Debugger}.
+ While a sentinel is running, the process sentinel is temporarily
+set to @code{nil} so that the sentinel won't run recursively.
+For this reason it is not possible for a sentinel to specify
+a new sentinel.
+
In earlier Emacs versions, every sentinel that did regular expression
searching or matching had to explicitly save and restore the match data.
Now Emacs does this automatically for sentinels; they never need to do