From: Eli Zaretskii <eliz@gnu.org>
To: Ivan Andrus <darthandrus@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Callbacks from modules
Date: Fri, 27 Nov 2015 10:29:09 +0200 [thread overview]
Message-ID: <837fl3u9pm.fsf@gnu.org> (raw)
In-Reply-To: <C84B3EF3-49B8-4489-9B30-0ACB7C229E22@gmail.com>
> From: Ivan Andrus <darthandrus@gmail.com>
> Date: Thu, 26 Nov 2015 20:23:48 -0700
> Cc: emacs-devel@gnu.org
>
> > Then one way would be to have that callback set a flag,
> > provide a Lisp-callable function that returns the flag, and then start
> > a timer that will test the flag and call your Lisp callback when the
> > flag is set.
>
> I was hoping to avoid polling, since the use case I have would like to start reading again as soon as the previous version finishes.
You could do that on the C level, no? You don't need anything from
Lisp to start reading again.
> > Another, perhaps simpler, possibility would be to have the module
> > provide a Lisp-callable function that will register a Lisp callback.
> > Then your C callback will simply call that Lisp function.
>
> I don’t understand how I would implement this option, though it sounds like what I was hoping for. In order to call a lisp function, don’t I need an emacs_env?
Forget it, it probably won't work anyway, because your C callback runs
in another thread, right? Module code cannot run in any thread but
the main thread.
next prev parent reply other threads:[~2015-11-27 8:29 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 6:08 Callbacks from modules Ivan Andrus
2015-11-26 15:43 ` Eli Zaretskii
2015-11-26 16:17 ` joakim
2015-11-26 16:33 ` Eli Zaretskii
2015-11-26 17:01 ` Philipp Stephani
2015-11-26 17:19 ` Eli Zaretskii
2015-11-27 3:23 ` Ivan Andrus
2015-11-27 8:29 ` Eli Zaretskii [this message]
2015-11-27 17:30 ` Ivan Andrus
2015-11-26 18:16 ` Philipp Stephani
2015-11-26 18:41 ` Eli Zaretskii
2015-11-26 18:44 ` Philipp Stephani
2015-11-27 3:35 ` Ivan Andrus
2015-11-27 8:30 ` Eli Zaretskii
2015-11-27 17:31 ` Ivan Andrus
2015-11-27 4:22 ` Tom Tromey
2015-11-27 8:35 ` Eli Zaretskii
2015-11-30 14:03 ` Ted Zlatanov
2015-11-30 15:58 ` Eli Zaretskii
2015-11-30 16:52 ` John Wiegley
2015-11-27 4:20 ` Tom Tromey
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=837fl3u9pm.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=darthandrus@gmail.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 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.