From: Eli Zaretskii <eliz@gnu.org>
To: Ivan Yonchovski <yyoncho@gmail.com>
Cc: 42028@debbugs.gnu.org
Subject: bug#42028: [Feature Request] 27.0.91; Provide the ability dynamic modules to post events in emacs event loop
Date: Wed, 24 Jun 2020 17:44:42 +0300 [thread overview]
Message-ID: <83bll8ttet.fsf@gnu.org> (raw)
In-Reply-To: <875zbh0wbf.fsf@gmail.com> (message from Ivan Yonchovski on Wed, 24 Jun 2020 10:14:44 +0300)
> From: Ivan Yonchovski <yyoncho@gmail.com>
> Date: Wed, 24 Jun 2020 10:14:44 +0300
>
> This is needed for the cases when the module is listening for extenal
> events and wants to call back emacs to process them. ATM this is kind of
> possible by using signals on linux and using WM_INPUTLANGCHANGE as
> described in https://nullprogram.com/blog/2017/02/14/ but this looks
> more a hack for a missing feature.
It is almost trivial to let modules insert events into the event
queue. The problem is that I expect a module that inserts such events
to want to be called to process those events as well. Is that
expectation correct? If it is, then we need to think about extending
the mechanism that calls event handlers, not just about exposing the
likes of kbd_buffer_store_event to modules. We should also consider
how a module could define its own events.
IOW, this calls for a slightly more detailed specification, before
someone could sit down and code the stuff. I suggest to take a look
at how existing events are handled, and propose such a detailed
specification.
Thanks.
next prev parent reply other threads:[~2020-06-24 14:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 7:14 bug#42028: [Feature Request] 27.0.91; Provide the ability dynamic modules to post events in emacs event loop Ivan Yonchovski
2020-06-24 14:44 ` Eli Zaretskii [this message]
2020-06-24 16:17 ` yyoncho
2020-06-24 16:28 ` Eli Zaretskii
2020-06-24 16:46 ` yyoncho
2020-06-24 17:07 ` Eli Zaretskii
2020-06-24 17:33 ` Ivan Yonchovski
2020-06-24 18:04 ` Eli Zaretskii
2020-06-24 18:38 ` Ivan Yonchovski
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=83bll8ttet.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=42028@debbugs.gnu.org \
--cc=yyoncho@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).