all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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 12:05:12 +0200	[thread overview]
Message-ID: <87pnyluuuf.fsf@gmx.de> (raw)
In-Reply-To: <83sh3ijpql.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 13 Aug 2018 17:38:42 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

Hi Eli,

> I don't know, the discussion never reached any concrete conclusions.
> (And the more I think about that, the less I understand how a message
> pump could help: after all, keyboard input is already a kind of
> "message pump", on the OS level.  It seems we'd eventually have the
> same problem: how to allow multiple threads to read from the message
> pump.)
>
> Some additional discussion was in this thread:
>
>   http://lists.gnu.org/archive/html/emacs-devel/2016-12/msg00607.html
>
> Maybe we need to start a new discussion on emacs-devel, once you read
> that.

Yes, that's needed. I have also no idea how to fix. 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.

Perhaps we need this also for other events, D-Bus and file notifications
come to mind.

I fear I'm not the best one to reanimate this discussion. Keyboard
handling in Emacs is terra incognita for me.

Best regards, Michael.





  reply	other threads:[~2018-08-14 10:05 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 [this message]
2018-08-14 15:16         ` Eli Zaretskii
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=87pnyluuuf.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 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.