summaryrefslogtreecommitdiff
path: root/doc/lispref/threads.texi
diff options
context:
space:
mode:
authorTom Tromey <tromey@redhat.com>2012-08-24 09:28:02 -0600
committerTom Tromey <tromey@redhat.com>2012-08-24 09:28:02 -0600
commit58c8e9a4debc3ef2c672a34d58720d5bf0530d12 (patch)
tree2145d3f082b2a9d8b8e8a5414cebc0bd2bd903c6 /doc/lispref/threads.texi
parentc2283a75564d7794fb5f604eafc6b65f71146e7f (diff)
downloademacs-58c8e9a4debc3ef2c672a34d58720d5bf0530d12.tar.gz
minor documentation updates
Diffstat (limited to 'doc/lispref/threads.texi')
-rw-r--r--doc/lispref/threads.texi6
1 files changed, 5 insertions, 1 deletions
diff --git a/doc/lispref/threads.texi b/doc/lispref/threads.texi
index 8094a68f9aa..434915cdbc2 100644
--- a/doc/lispref/threads.texi
+++ b/doc/lispref/threads.texi
@@ -27,7 +27,8 @@ also to create and control mutexes and condition variables, useful for
thread synchronization.
While global variables are shared among all Emacs Lisp threads,
-local variables are not---a dynamic @code{let} binding is local.
+local variables are not---a dynamic @code{let} binding is local. Each
+thread also has its own current buffer (@pxref{Current Buffer}).
In the case of lexical bindings (@pxref{Variable Scoping}), a
closure is an object like any other in Emacs Lisp, and bindings in a
@@ -50,6 +51,9 @@ threads can be signaled.
Create a new thread of execution which invokes @var{function}. When
@var{function} returns, the thread exits.
+The new thread is created with no local variable bindings in effect.
+The new thread's current buffer is inherited from the current thread.
+
@var{name} can be supplied to give a name to the thread. The name is
used for debugging and informational purposes only; it has no meaning
to Emacs. If @var{name} is provided, it must be a string.