From: Eli Zaretskii <eliz@gnu.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: luangruo@yahoo.com, 53432@debbugs.gnu.org,
ijackson@chiark.greenend.org.uk
Subject: bug#53432: [PATCH] Avoid losing keyboard input when inotify is too busy [and 1 more messages]
Date: Mon, 24 Jan 2022 19:25:00 +0200 [thread overview]
Message-ID: <83a6fljbbn.fsf@gnu.org> (raw)
In-Reply-To: <877daprrbn.fsf@gmx.de> (message from Michael Albinus on Mon, 24 Jan 2022 18:12:12 +0100)
> From: Michael Albinus <michael.albinus@gmx.de>
> Cc: ijackson@chiark.greenend.org.uk, luangruo@yahoo.com,
> 53432@debbugs.gnu.org
> Date: Mon, 24 Jan 2022 18:12:12 +0100
>
> >> "Key strokes first!" :-)
> >
> > But it isn't only the key strokes, it's also all the events sent to us
> > by the window-system. Now tell me why, say, an expose event should be
> > more important than a file-notification event, and not the other way
> > around?
>
> After all, Emacs is still a text editor, isn't it? Key strokes and mouse
> events are the most important events, I believe.
I agree, but since window-system events come from the same source as
keys and mouse, we don't have a good way of processing "keys and mouse
first", do we? We can only process everything that comes from the
read_socket_hook before file notification (which would mean "keys,
mouse, and window-system events first"), or the other way around.
So the question whether a window-system event is more or less
important than a file-notification event still stands, and has no easy
solution if we start reading events from two queues instead of just
one.
> As rule of thumb, I would discriminate all events, which can aarive as
> burst, and which are already known to be lost sometimes. D-Bus and file
> notification events. If we classify other events into this category - no
> problem.
That's okay (and note that w32notify already does drop excess events
on the floor).
next prev parent reply other threads:[~2022-01-24 17:25 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 23:36 bug#53432: [PATCH] Avoid losing keyboard input when inotify is too busy Ian Jackson
2022-01-22 0:38 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-22 19:34 ` bug#53432: [PATCH] Avoid losing keyboard input when inotify is too busy [and 1 more messages] Ian Jackson
2022-01-22 19:48 ` Eli Zaretskii
2022-01-23 2:37 ` Dmitry Gutov
2022-01-23 2:47 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-23 2:49 ` Dmitry Gutov
2022-01-23 2:53 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-23 3:23 ` Dmitry Gutov
2022-01-23 3:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-23 3:36 ` Dmitry Gutov
2022-01-23 3:48 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-23 4:07 ` Dmitry Gutov
2022-01-23 5:50 ` Eli Zaretskii
2022-01-23 16:34 ` Michael Albinus
2022-01-23 1:00 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-23 13:38 ` Ian Jackson
2022-01-23 16:37 ` Michael Albinus
2022-01-23 18:31 ` Ian Jackson
2022-01-24 0:42 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-24 14:42 ` Michael Albinus
2022-01-24 14:57 ` Eli Zaretskii
2022-01-24 15:35 ` Michael Albinus
2022-01-24 16:52 ` Eli Zaretskii
2022-01-24 17:12 ` Michael Albinus
2022-01-24 17:25 ` Eli Zaretskii [this message]
2022-01-24 15:45 ` Ian Jackson
2022-01-24 17:05 ` Michael Albinus
2022-01-24 18:59 ` Ian Jackson
2022-01-25 14:50 ` Michael Albinus
2022-01-24 0:26 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-22 6:45 ` bug#53432: [PATCH] Avoid losing keyboard input when inotify is too busy Eli Zaretskii
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=83a6fljbbn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53432@debbugs.gnu.org \
--cc=ijackson@chiark.greenend.org.uk \
--cc=luangruo@yahoo.com \
--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.