all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: jch@irif.fr, emacs-devel@gnu.org
Subject: Re: semantics of thread-signal
Date: Mon, 12 Dec 2016 18:08:11 +0200	[thread overview]
Message-ID: <83k2b5ceqc.fsf@gnu.org> (raw)
In-Reply-To: <CAM-tV--TwYcv3GRH3HgV0Xzk7va3cO8bqQBrbxiJgmT4H09KnQ@mail.gmail.com> (message from Noam Postavsky on Sun, 11 Dec 2016 21:06:38 -0500)

> From: Noam Postavsky <npostavs@users.sourceforge.net>
> Date: Sun, 11 Dec 2016 21:06:38 -0500
> Cc: Emacs developers <emacs-devel@gnu.org>
> 
> --- i/doc/lispref/threads.texi
> +++ w/doc/lispref/threads.texi
> @@ -82,9 +82,11 @@ Basic Thread Functions
>  @defun thread-signal thread error-symbol data
>  Like @code{signal} (@pxref{Signaling Errors}), but the signal is
>  delivered in the thread @var{thread}.  If @var{thread} is the current
> -thread, then this just calls @code{signal} immediately.
> -@code{thread-signal} will cause a thread to exit a call to
> -@code{mutex-lock}, @code{condition-wait}, or @code{thread-join}.
> +thread, then this just calls @code{signal} immediately.  Otherwise,
> +@var{thread} will receive the signal as soon as it becomes current.
> +If @var{thread} was blocked by a call to @code{mutex-lock},
> +@code{condition-wait}, or @code{thread-join}; @code{thread-signa} will
> +unblock it.                                         ^^^^^^^^^^^^
>  @end defun

Thanks, please push after fixing the typo.



  reply	other threads:[~2016-12-12 16:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-12  0:16 semantics of thread-signal (WAS: Crashing the new thread code) Noam Postavsky
2016-12-12  1:21 ` semantics of thread-signal Juliusz Chroboczek
2016-12-12  2:06   ` Noam Postavsky
2016-12-12 16:08     ` Eli Zaretskii [this message]
2016-12-13  2:46       ` Noam Postavsky
2016-12-12  3:33   ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83k2b5ceqc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jch@irif.fr \
    --cc=npostavs@users.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.