From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Akira Kyle <ak@akirakyle.com>
Cc: emacs-devel@gnu.org
Subject: Re: "Asynchronous Requests from Emacs Dynamic Modules"
Date: Fri, 30 Oct 2020 18:39:55 -0400 [thread overview]
Message-ID: <jwva6w38hs9.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <86imarfldb.fsf@akirakyle.com> (Akira Kyle's message of "Fri, 30 Oct 2020 15:35:12 -0600")
> Does anyone know of the best way to handle this?
> Perhaps the module interface should be expanded to handle this situation?
Most likely, we need some way for a module to "raise a flag" which then
causes the main Lisp thread to get back to the module.
Maybe the best way to do that is for the module to create a ELisp
"process" object with a corresponding file handle (probably a fifo, with
one end used by the ELisp process object and the other end used by the
module), so when the module needs to run an async request, it would
write to the fifo, and then the process's `process-filter` would call
the module back to actually process the async request.
Stefan
next prev parent reply other threads:[~2020-10-30 22:39 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 21:35 "Asynchronous Requests from Emacs Dynamic Modules" Akira Kyle
2020-10-30 22:39 ` Stefan Monnier [this message]
2020-10-31 3:18 ` Zhu Zihao
2020-10-31 7:45 ` Eli Zaretskii
2020-10-31 8:02 ` yyoncho
2020-10-31 9:13 ` Eli Zaretskii
2020-10-31 9:45 ` yyoncho
2020-10-31 10:43 ` Eli Zaretskii
2020-10-31 19:25 ` Akira Kyle
2020-10-31 20:18 ` Eli Zaretskii
2020-11-01 0:14 ` Akira Kyle
2020-11-01 18:28 ` Eli Zaretskii
2020-11-01 20:15 ` Akira Kyle
2020-11-01 20:51 ` async-await (was: Re: "Asynchronous Requests from Emacs Dynamic Modules") Philipp Stephani
2020-11-02 15:22 ` "Asynchronous Requests from Emacs Dynamic Modules" Eli Zaretskii
2020-10-31 7:36 ` Philipp Stephani
2020-10-31 12:49 ` Stefan Monnier
2020-11-01 20:18 ` Akira Kyle
2020-11-01 20:32 ` Philipp Stephani
2020-11-20 15:54 ` Zhu Zihao
2020-11-20 16:04 ` Robert Pluim
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=jwva6w38hs9.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=ak@akirakyle.com \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).