From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings Newsgroups: gmane.emacs.bugs 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-ID: References: <834jx85tyv.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="SdnpM173OW" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="21058"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , 57804@debbugs.gnu.org, Lars Ingebrigtsen To: Paul Pogonyshev Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Sep 16 01:14:11 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oYy3f-0005JU-A0 for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 16 Sep 2022 01:14:11 +0200 Original-Received: from localhost ([::1]:60970 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oYy3d-00083X-GH for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 15 Sep 2022 19:14:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55994) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oYy3W-00083M-K6 for bug-gnu-emacs@gnu.org; Thu, 15 Sep 2022 19:14:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:42586) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oYy3W-0000DJ-CM for bug-gnu-emacs@gnu.org; Thu, 15 Sep 2022 19:14:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oYy3V-0002UO-Kk for bug-gnu-emacs@gnu.org; Thu, 15 Sep 2022 19:14:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Gregory Heytings Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 15 Sep 2022 23:14:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 57804 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: wontfix Original-Received: via spool by 57804-submit@debbugs.gnu.org id=B57804.16632836189527 (code B ref 57804); Thu, 15 Sep 2022 23:14:01 +0000 Original-Received: (at 57804) by debbugs.gnu.org; 15 Sep 2022 23:13:38 +0000 Original-Received: from localhost ([127.0.0.1]:59518 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oYy38-0002Tb-2L for submit@debbugs.gnu.org; Thu, 15 Sep 2022 19:13:38 -0400 Original-Received: from heytings.org ([95.142.160.155]:43394) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oYy32-0002TP-Dr for 57804@debbugs.gnu.org; Thu, 15 Sep 2022 19:13:36 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1663283611; bh=fu5RvgNrS4WqN8gtpIa4/+2mbR0kfKkrFUAsgaApl2Q=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=WpeAej+ldkKr1Jku9J3q6Q/vczM+/i5jGWzkwjg7XlXLzRaBwdf644QnLO7AXVH+6 MjGATTW0xqW9NhHcyT6L5UqrRexcUlTrWkIBoKY82GYPf9uW0Oahs+mU4ChMIJxFjt anc8osE2j9Xjdp/TJtcfDXAmlo4y4NvvHsW+I3X9LR38u5ttYaP3fP901DnSzN4tsy wpBmKHFRGW8RYnW3mLt/J491QDZ8BQ1oAhk9K63NruWuT0eCLYK/HYHC0SktG394BM XFd9MMI5QZjLXw2mFIUHlV53APU32COvnlB/Ors1tzf/JksHAQx2q6DnfwUAQABsqF KI2vlOzKldA5A== In-Reply-To: Content-ID: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:242668 Archived-At: --SdnpM173OW Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable Content-ID: >> I also cannot understand why it is necessary, in log files in which all= =20 >> lines are independent >=20 > No they are not. Typically Java exceptions are logged like this: >=20 > =C2=A0 =C2=A0 2022-09-15 23:11:00.014 ERROR [some.Class] (some-thread) bl= a-bla-bla > =C2=A0 =C2=A0 exception.Class: bla-bla-bla > =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 at some.Class >=20 > 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= =20 at any time, does it? You do not need to go further than the beginning of= =20 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=20 > 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= =20 > all in general case. > If it is possible to unlock a locked narrowing, and if it is possible to=20 disable locked narrowing completely, nothing is prevented. --SdnpM173OW--