GNU bug report logs - #57804
An infinite loop in a `fontify-region' function causes Emacs to hang indefinitely

Previous Next

Package: emacs;

Reported by: Paul Pogonyshev <pogonyshev <at> gmail.com>

Date: Wed, 14 Sep 2022 15:07:01 UTC

Severity: normal

Tags: wontfix

Done: Eli Zaretskii <eliz <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Gregory Heytings <gregory <at> heytings.org>
To: Paul Pogonyshev <pogonyshev <at> gmail.com>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 57804 <at> debbugs.gnu.org, Lars Ingebrigtsen <larsi <at> gnus.org>
Subject: bug#57804: An infinite loop in a `fontify-region' function causes Emacs to hang indefinitely
Date: Thu, 15 Sep 2022 23:13:30 +0000
[Message part 1 (text/plain, inline)]
>> I also cannot understand why it is necessary, in log files in which all 
>> lines are independent
> 
> No they are not. Typically Java exceptions are logged like this:
> 
>     2022-09-15 23:11:00.014 ERROR [some.Class] (some-thread) bla-bla-bla
>     exception.Class: bla-bla-bla
>           at some.Class
> 
> and so on. Exceptions are not the only multiline entries.
>

Okay, but that still doesn't mean that you need to access the whole buffer 
at any time, does it?  You do not need to go further than the beginning of 
the "2022-09-15 23:11:00.014 ERROR..." line, or am I missing something?

>
> I have already complained about this often-seen-here "I also cannot 
> understand", which implies "therefore no-one will ever need"
>

No, that's not what it implies.  It is a request for clarification.

>
> By trying to prevent "making it too easily", you are preventing this at 
> all in general case.
>

If it is possible to unlock a locked narrowing, and if it is possible to 
disable locked narrowing completely, nothing is prevented.

This bug report was last modified 2 years and 230 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.