From c1456e303a4502f637a87681dd623f589c25ed23 Mon Sep 17 00:00:00 2001 From: Tom Tromey Date: Tue, 27 Aug 2013 13:07:14 -0600 Subject: [PATCH] zap until-condition docs --- doc/lispref/threads.texi | 9 +-------- 1 file changed, 1 insertion(+), 8 deletions(-) diff --git a/doc/lispref/threads.texi b/doc/lispref/threads.texi index c846993172f..b3a70ee215c 100644 --- a/doc/lispref/threads.texi +++ b/doc/lispref/threads.texi @@ -192,8 +192,7 @@ and waiting on the condition variable. For example: @end example The mutex ensures atomicity, and the loop is for robustness---there -may be spurious notifications. Emacs Lisp provides a macro, -@code{until-condition}, to do this automatically. +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 @@ -251,9 +250,3 @@ Return the name of @var{cond}, as passed to Return the mutex associated with @var{cond}. Note that the associated mutex cannot be changed. @end defun - -@defmac until-condition test cond -Acquire the mutex associated with @var{cond}, and then loop, invoking -the form @var{test}. If @var{test} evaluates to @code{nil}, invoke -@code{condition-wait} on @var{cond}. -@end defmac -- 2.39.2