From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 32426@debbugs.gnu.org
Subject: bug#32426: 27.0.50; Loosing key bindings in threads
Date: Tue, 14 Aug 2018 18:16:00 +0300 [thread overview]
Message-ID: <837ektj7wv.fsf@gnu.org> (raw)
In-Reply-To: <87pnyluuuf.fsf@gmx.de> (message from Michael Albinus on Tue, 14 Aug 2018 12:05:12 +0200)
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: 32426@debbugs.gnu.org
> Date: Tue, 14 Aug 2018 12:05:12 +0200
>
> > Maybe we need to start a new discussion on emacs-devel, once you read
> > that.
>
> Yes, that's needed.
Started a discussion on emacs-devel.
> But I know that the proposal to disable keyboard reading for all
> threads but the main one is not working; see my example in
> bug#32426.
I'm not surprised.
> 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.
By contrast, there's only one keyboard descriptor.
next prev parent reply other threads:[~2018-08-14 15:16 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 [this message]
2018-08-14 15:48 ` Michael Albinus
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=837ektj7wv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=32426@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
/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.