From: Eli Zaretskii <eliz@gnu.org>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: 69561@debbugs.gnu.org, alan@idiocy.org
Subject: bug#69561: 30.0.50; Freeze from M-x gnus on macOS
Date: Sat, 09 Mar 2024 15:27:43 +0200 [thread overview]
Message-ID: <86a5n7y1ps.fsf@gnu.org> (raw)
In-Reply-To: <m2o7bny20d.fsf@Pro.fritz.box> (message from Gerd Möllmann on Sat, 09 Mar 2024 14:21:22 +0100)
> From: Gerd Möllmann <gerd.moellmann@gmail.com>
> Cc: alan@idiocy.org, 69561@debbugs.gnu.org
> Date: Sat, 09 Mar 2024 14:21:22 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> Right, sorry, C-g came only into play because I tbought the current
> >> sitution might become bearable if it could at least be interrupted with
> >> C-g. And then I understoof the drama better.
> >>
> >> If you take a look at the first hunk of the patch I sent, you can see
> >> that ns_select can do _nothing_ interesting at all, it just returns -1.
> >
> > But your patch still doesn't solve the problem, does it?
>
> I'd say it does:
>
> - it ensures that a "real" select is called, which formerly wasn't
> guaranteed
>
> - it makes sure that queued input_events are passed to Emacs, for C-g
> detection, Vquit_flag and so on.
>
> - it makes sure NS events are processed, so that C-g has a chance to get
> into the queued input_events in the first place, from processing
> keyDown events.
In that case, I think you should proceed by collecting experience with
this patch. If the freezes indeed go away, then I think you should
install it.
next prev parent reply other threads:[~2024-03-09 13:27 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 10:59 bug#69561: 30.0.50; Freeze from M-x gnus on macOS Gerd Möllmann
2024-03-05 11:04 ` Gerd Möllmann
2024-03-05 14:29 ` Gerd Möllmann
2024-03-05 15:46 ` Eli Zaretskii
2024-03-05 16:38 ` Gerd Möllmann
2024-03-05 16:52 ` Eli Zaretskii
2024-03-05 17:54 ` Gerd Möllmann
2024-03-07 15:18 ` Gerd Möllmann
2024-03-07 15:52 ` Gerd Möllmann
2024-03-07 16:05 ` Alan Third
2024-03-07 16:30 ` Gerd Möllmann
2024-03-07 16:49 ` Alan Third
2024-03-07 17:01 ` Gerd Möllmann
2024-03-07 18:47 ` Alan Third
2024-03-07 19:29 ` Gerd Möllmann
2024-03-07 20:23 ` Gerd Möllmann
2024-03-08 4:31 ` Gerd Möllmann
2024-03-09 7:33 ` Eli Zaretskii
2024-03-09 9:47 ` Gerd Möllmann
2024-03-09 10:07 ` Eli Zaretskii
2024-03-09 11:00 ` Gerd Möllmann
2024-03-09 11:11 ` Eli Zaretskii
2024-03-09 11:33 ` Gerd Möllmann
2024-03-09 13:08 ` Eli Zaretskii
2024-03-09 13:21 ` Gerd Möllmann
2024-03-09 13:27 ` Eli Zaretskii [this message]
2024-03-09 13:51 ` Gerd Möllmann
2024-03-13 6:11 ` Gerd Möllmann
2024-03-13 16:53 ` Filipp Gunbin
2024-03-13 18:18 ` Gerd Möllmann
2024-03-13 18:20 ` Gerd Möllmann
2024-03-13 19:20 ` Filipp Gunbin
2024-03-13 19:37 ` Gerd Möllmann
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=86a5n7y1ps.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=69561@debbugs.gnu.org \
--cc=alan@idiocy.org \
--cc=gerd.moellmann@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 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.