From: Eli Zaretskii <eliz@gnu.org>
To: Devon Sean McCullough <Emacs-hacker2018@jovi.net>
Cc: 44818@debbugs.gnu.org
Subject: bug#44818: 27.0.91; wedged
Date: Wed, 25 Nov 2020 17:06:02 +0200 [thread overview]
Message-ID: <83v9dtsch1.fsf@gnu.org> (raw)
In-Reply-To: <d13a053f-377b-0ab0-bb68-d168c24171cd@jovi.net> (message from Devon Sean McCullough on Tue, 24 Nov 2020 20:35:00 -0500)
> Cc: 44818@debbugs.gnu.org
> From: Devon Sean McCullough <Emacs-hacker2018@jovi.net>
> Date: Tue, 24 Nov 2020 20:35:00 -0500
>
> On 24/11/2020 13:48, Eli Zaretskii wrote:
> >> Cc: 44818@debbugs.gnu.org
> >> From: Devon Sean McCullough <Emacs-hacker2018@jovi.net>
> >> Date: Tue, 24 Nov 2020 13:42:03 -0500
> >>
> >> P.S. Could a watchdog timer safely abort such wedgitude?
> >
> > That would have to run in a separate thread, right?
> >
> > But what timeout to set it to? some jobs might legitimately take some
> > time. And then what to do when the timer expires?
>
> The job of redisplay cannot legitimately take > 50 milliseconds.
It can, and it does. Although this is quite rare, it does happen.
Here's a simple example: visit src/xdisp.c, then type M-> and measure
the time.
> When the user repeatedly tries ^G quit but Emacs is unresponsive
> because of redisplay, such redisplay must be prevented while the
> user is offered options to regain control.
I asked "what to do when the timer expires" because the practical
meaning of "redisplay must be prevented" is not at all clear.
> P.S. Could an invisibility overlay offer temporary relief?
> Perhaps a red screen of redisplay death with a short menu?
Anything that has to be done by the display code will suffer from the
same problem.
next prev parent reply other threads:[~2020-11-25 15:06 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 1:04 bug#44809: One very long line of <中文> XML tags puts emacs out of business 積丹尼 Dan Jacobson
2020-11-24 7:05 ` Lars Ingebrigtsen
2020-11-27 19:43 ` bug#44809: Warn that current file needs so-long mode 積丹尼 Dan Jacobson
[not found] ` <handler.s.C.160651363628407.transcript@debbugs.gnu.org>
2020-11-23 5:07 ` bug#44818: 27.0.91; wedged Devon Sean McCullough
2020-11-23 15:51 ` Eli Zaretskii
2020-11-24 7:04 ` Lars Ingebrigtsen
2020-11-24 15:39 ` Eli Zaretskii
2020-11-25 6:57 ` Lars Ingebrigtsen
2020-11-25 15:37 ` Eli Zaretskii
2020-11-24 18:42 ` Devon Sean McCullough
2020-11-24 18:48 ` Eli Zaretskii
2020-11-25 1:35 ` Devon Sean McCullough
2020-11-25 8:34 ` Andreas Schwab
2020-11-25 14:47 ` Devon Sean McCullough
2020-11-25 15:06 ` Eli Zaretskii [this message]
2020-11-26 17:06 ` Devon Sean McCullough
2020-11-27 5:40 ` Richard Stallman
2020-12-01 11:32 ` Devon Sean McCullough
2020-12-02 4:32 ` Richard Stallman
2020-12-02 15:00 ` Eli Zaretskii
2020-12-03 5:29 ` Richard Stallman
2020-12-03 14:53 ` Eli Zaretskii
2020-12-04 6:01 ` Richard Stallman
2020-12-04 8:36 ` Eli Zaretskii
2020-11-27 8:20 ` Michael Albinus
2020-11-27 22:26 ` bug#44818: Looks like I retitled both bugs 積丹尼 Dan Jacobson
2020-11-29 9:50 ` bug#44809: Warn that current file needs so-long mode Lars Ingebrigtsen
2022-07-23 8:56 ` bug#44818: Say "Consider switching so-long mode on" when detecting long line files Lars Ingebrigtsen
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=83v9dtsch1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44818@debbugs.gnu.org \
--cc=Emacs-hacker2018@jovi.net \
/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).