From: Ivan Andrus <darthandrus@gmail.com>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, dancol@dancol.org, emacs-devel@gnu.org
Subject: Re: Callbacks from modules
Date: Thu, 26 Nov 2015 20:35:06 -0700 [thread overview]
Message-ID: <AAE0703C-8559-4C5A-8284-3D9AACABEF26@gmail.com> (raw)
In-Reply-To: <CAArVCkTZ4Q-nVUoAjjViGHe+3KQaHcbGrdgn_H4V8aaQytcmFg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 721 bytes --]
On Nov 26, 2015, at 11:44 AM, Philipp Stephani <p.stephani2@gmail.com> wrote:
>
> IOW, such arbitrary callbacks need to run in the C land, and
> communicate with Lisp via timers. In the future, we might add
> facilities that would allow a module register a file descriptor
> through which events could flow into the Emacs event queue. But that
> is not yet available, and I'm not sure we'd want to allow it.
>
> I agree.
It seems desirable to me to have a function
void send_event( char const * type );
which would just queue a special type of event that could be dispatched on the elisp side through the normal even handling. Though I admit I don’t really understand how it all works.
-Ivan
[-- Attachment #2: Type: text/html, Size: 2532 bytes --]
next prev parent reply other threads:[~2015-11-27 3:35 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
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 [this message]
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
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=AAE0703C-8559-4C5A-8284-3D9AACABEF26@gmail.com \
--to=darthandrus@gmail.com \
--cc=dancol@dancol.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=p.stephani2@gmail.com \
/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).