From: David Kastrup <dak@gnu.org>
Subject: Re: Mutual exclusion in Emacs
Date: 25 May 2004 09:47:39 +0200 [thread overview]
Message-ID: <x5u0y5uew4.fsf@lola.goethe.zz> (raw)
In-Reply-To: vpqpt8tt2nb.fsf@ecrins.imag.fr
Matthieu Moy <MatthieuNOSPAM.Moy@imag.fr.invalid> writes:
> How is concurrency managed in Emacs? I know there's no threading
> support, but since you can launch several asynchronous processes, with
> process sentinels, is there a risk that a process sentinel preempt the
> non-process-sentinel code being executed, or another processes
> sentinel.
>
> If so, is there a way to guaranty mutual exclusion if all the process
> sentinels access a common ressource?
Is there anything wrong with the Elisp manual? I thought it was
explained pretty thoroughly just at what points of time sentinels may
get run.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2004-05-25 7:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 6:57 Mutual exclusion in Emacs Matthieu Moy
2004-05-25 7:47 ` David Kastrup [this message]
2004-05-25 21:44 ` Matthieu Moy
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x5u0y5uew4.fsf@lola.goethe.zz \
--to=dak@gnu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).