From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 32426@debbugs.gnu.org
Subject: bug#32426: 27.0.50; Loosing key bindings in threads
Date: Tue, 14 Aug 2018 17:48:22 +0200 [thread overview]
Message-ID: <87eff1ueyh.fsf@gmx.de> (raw)
In-Reply-To: <837ektj7wv.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 14 Aug 2018 18:16:00 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
Hi Eli,
>> Perhaps we need this also for other events, D-Bus and file notifications
>> come to mind.
>
> Possibly, but those seem like an easier nut to crack: AFAIU, each time
> we need to watch for D-Bus events, we register a file descriptor for
> that, and deregister it when we no longer need it, is that right? If
> so, we could easily make these descriptors watched only by the thread
> that registered the watch, the infrastructure for that already exists.
We need a file descriptor per D-Bus bus (system and session). But
applications register for (asynchronous) method calls and signals on the
buses. This could happen in several threads, so we need a mechanism how
to distribute incoming events to those threads.
But I would postpone this discussion until after we have resolved the
keyboard issue.
Best regards, Michael.
prev parent reply other threads:[~2018-08-14 15:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 8:40 bug#32426: 27.0.50; Loosing key bindings in threads Michael Albinus
2018-08-13 9:39 ` Eli Zaretskii
2018-08-13 12:17 ` Michael Albinus
2018-08-13 14:38 ` Eli Zaretskii
2018-08-14 10:05 ` Michael Albinus
2018-08-14 15:16 ` Eli Zaretskii
2018-08-14 15:48 ` Michael Albinus [this message]
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=87eff1ueyh.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=32426@debbugs.gnu.org \
--cc=eliz@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).