From 0e82377a2d9d8f815d2ef4ec09dc914f37fc87ac Mon Sep 17 00:00:00 2001 From: Tom Tromey Date: Tue, 27 Aug 2013 13:10:59 -0600 Subject: [PATCH] use condition-notify in the docs, not condition-signal --- doc/lispref/threads.texi | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/lispref/threads.texi b/doc/lispref/threads.texi index b3a70ee215c..6237392db3a 100644 --- a/doc/lispref/threads.texi +++ b/doc/lispref/threads.texi @@ -196,12 +196,12 @@ may be spurious notifications. Similarly, the mutex must be held before notifying the condition. The typical, and best, approach is to acquire the mutex, make the -changes associated with this condition, and then signal it: +changes associated with this condition, and then notify it: @example (with-mutex mutex (setq global-variable (some-computation)) - (condition-signal cond-var)) + (condition-notify cond-var)) @end example @defun make-condition-variable mutex &optional name -- 2.39.2