From: tomas@tuxteam.de
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Fun with async processes
Date: Tue, 1 Feb 2022 15:31:19 +0100 [thread overview]
Message-ID: <YflEN2hu15C8ceRO@tuxteam.de> (raw)
In-Reply-To: <87v8xy3d5g.fsf@elite.giraud>
[-- Attachment #1: Type: text/plain, Size: 1106 bytes --]
On Tue, Feb 01, 2022 at 02:54:51PM +0100, Manuel Giraud wrote:
> tomas@tuxteam.de writes:
>
> [...]
>
> > Nice. Many ways to go about that.
>
> And do you think I could avoid having those defvar?
How about hiding stuff in a closure? You'll need to have lexical
environments for that:
(defun make-sentinel-factory ()
(let (sentinels (list))
(lambda (tag)
(setq sentinels (push tag sentinels)) ; FIXME: fail if already there!
(lambda (process event)
(when (equal "finished" event)
(setq sentinels (delq tag sentinels))
(message "%S is done; still left: %S" tag sentinels)
(when (null sentinels)
(message "All sentinels done")))))))
(setq make-sentinel (make-sentinel-factory))
(setq s1 (funcall make-sentinel 's1))
(setq s2 (funcall make-sentinel 's2))
(setq s3 (funcall make-sentinel 's3))
(funcall s2 "process" "finished")
(funcall s3 "process" "finished")
(funcall s1 "process" "finished")
Catching errors is left as an exercise to ...
Cheers
--
t
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2022-02-01 14:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 15:44 Fun with async processes Manuel Giraud
2022-01-31 15:56 ` tomas
2022-01-31 17:11 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-31 17:49 ` tomas
2022-01-31 18:11 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-01 8:54 ` Manuel Giraud
2022-02-01 10:50 ` tomas
2022-02-01 13:30 ` Manuel Giraud
2022-02-01 13:43 ` tomas
2022-02-01 13:54 ` Manuel Giraud
2022-02-01 14:31 ` tomas [this message]
2022-02-01 23:10 ` Emanuel Berg via Users list for the GNU Emacs text editor
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=YflEN2hu15C8ceRO@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=help-gnu-emacs@gnu.org \
--cc=manuel@ledu-giraud.fr \
/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).