unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Mackenzie <acm@muc.de>
To: Po Lu <luangruo@yahoo.com>
Cc: "Gerd Möllmann" <gerd.moellmann@gmail.com>,
	59038@debbugs.gnu.org, "Eli Zaretskii" <eliz@gnu.org>,
	"Chris Hecker" <checker@d6.com>
Subject: bug#59038: loading this base64 file makes emacs -Q 28.2 peg a core infinitely
Date: Sat, 5 Nov 2022 22:03:51 +0000	[thread overview]
Message-ID: <Y2bdx1n+eUlsJPVs@ACM> (raw)
In-Reply-To: <87tu3dabbw.fsf@yahoo.com>

Hello, Po.

On Sat, Nov 05, 2022 at 19:29:39 +0800, Po Lu wrote:

[ .... ]

> All of this is no longer a problem in Emacs 29, and even if you somehow
> still cause redisplay to become wedged, you can set max-redisplay-ticks
> to a suitable value.

I looked that up in Emacs with C-h v.  It says it's the maximum number
of "redisplay ticks" before some aborting or other occurs.

I don't know what a redisplay tick is, and the dock string doesn't
explain it.  I've never heard of the term before.

This doc string is thus not very helpful, quite the reverse.

Maybe one of the manuals explains it.  It would be nice to have that
doc string amended to be less puzzling.

-- 
Alan Mackenzie (Nuremberg, Germany).





  parent reply	other threads:[~2022-11-05 22:03 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-05  2:48 bug#59038: loading this base64 file makes emacs -Q 28.2 peg a core infinitely Chris Hecker
2022-11-05  5:12 ` Gerd Möllmann
2022-11-05  7:01   ` Eli Zaretskii
2022-11-05  7:50     ` Gerd Möllmann
2022-11-05  8:21       ` Chris Hecker
2022-11-05  8:45         ` Gerd Möllmann
2022-11-05  9:30         ` Eli Zaretskii
2022-11-05 10:39           ` bug#59038: Re[2]: " Chris Hecker
2022-11-05 11:29         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-05 15:01           ` Chris Hecker
2022-11-06  5:17             ` Gerd Möllmann
2022-11-05 22:03           ` Alan Mackenzie [this message]
2022-11-06  6:00             ` Eli Zaretskii
2022-11-05  9:28       ` Eli Zaretskii
2022-11-06  5:18         ` Gerd Möllmann
2022-11-05 22:27     ` Gregory Heytings
2022-11-05 23:41       ` Gregory Heytings
2022-11-06  3:58         ` Phil Sainty
2022-11-06  5:20           ` Gerd Möllmann
2022-11-06 13:54             ` Alan Mackenzie
2022-11-06  9:18           ` Gregory Heytings
2022-11-06 13:52             ` Eli Zaretskii
2022-11-06 16:34               ` Alan Mackenzie
2022-11-07  7:55                 ` Gerd Möllmann
     [not found]               ` <Y2fiMTlfuNqae7zp@acm>
2022-11-06 19:46                 ` bug#59038: Re[2]: " Chris Hecker
2022-11-07 12:25                   ` Alan Mackenzie
2022-11-05  6:52 ` Eli Zaretskii
2022-11-05 10:45 ` Phil Sainty

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=Y2bdx1n+eUlsJPVs@ACM \
    --to=acm@muc.de \
    --cc=59038@debbugs.gnu.org \
    --cc=checker@d6.com \
    --cc=eliz@gnu.org \
    --cc=gerd.moellmann@gmail.com \
    --cc=luangruo@yahoo.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 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).