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 15:10:02 +0000 Message-ID: References: <87pmfx6h7y.fsf@gnus.org> <2b58b8f5429a6e3aecda@heytings.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="31294"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Lars Ingebrigtsen , 57804@debbugs.gnu.org To: Paul Pogonyshev Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Sep 15 17:11:21 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 1oYqWN-0007v5-R3 for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 15 Sep 2022 17:11:20 +0200 Original-Received: from localhost ([::1]:51764 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oYqWM-0001VF-HZ for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 15 Sep 2022 11:11:18 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:35296) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oYqW7-0001V7-K8 for bug-gnu-emacs@gnu.org; Thu, 15 Sep 2022 11:11:04 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:41943) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oYqW6-0000V8-IZ for bug-gnu-emacs@gnu.org; Thu, 15 Sep 2022 11:11:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oYqW6-0004o9-0h for bug-gnu-emacs@gnu.org; Thu, 15 Sep 2022 11:11:02 -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 15:11: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.166325461018396 (code B ref 57804); Thu, 15 Sep 2022 15:11:01 +0000 Original-Received: (at 57804) by debbugs.gnu.org; 15 Sep 2022 15:10:10 +0000 Original-Received: from localhost ([127.0.0.1]:58875 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oYqVG-0004me-56 for submit@debbugs.gnu.org; Thu, 15 Sep 2022 11:10:10 -0400 Original-Received: from heytings.org ([95.142.160.155]:42640) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oYqVA-0004mR-7Y for 57804@debbugs.gnu.org; Thu, 15 Sep 2022 11:10:08 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1663254602; bh=sUwiofaCTOCLTvgNlhoOTQH6N2MDpJJv4ZU2kO9PA6s=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=xpsXG8D0u0Sz5LhoBxNacJZKWm85aFXl1BqnIg3ztCeQGV3rkLupxpMLiuR7zmc6W chXhefOlA3Im8SeTxN4flXqK+XerdKKfbM9LJBDK3ql397iLB0ZAtcOhbve1HAbhMw EIPtv/o7Na5bUvIncj6kD0YGwg+FUI9exCGBO3riGN0ZIVvqWXgstLXFmRMdiVTVLH TunhvdNUAik7Pf//xCD2HeJ6t0xKhc5Oh6DyOSIeS29xjEdcxXWyF3q1+hwQodHy+m RNPlv3ZXsZjQafopMSnzE2IZ6qjOlgnZ6qOz1qyrEtovYHoOmc+XjU4cLGvDO9p8eP zb1FoGTGw3pPA== In-Reply-To: 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:242599 Archived-At: > > Is it technically impossible to lift narrowing restrictions in Emacs 29 > It is not, you can choose a radical approach and long-line-threshold to nil. Or you can choose a less radical approach and set long-line-threshold to a larger value (as I already told you twice IIRC). > > (as in, something would break), > Locked narrowing is one part of the solution to the long lines bug in Emacs, so something could indeed break if you turn that solution off. > > or is it "you have to rewrite, because we have decided so"? > That's not how I would present things, no. Why does Logview infloop when locked narrowing is in effect? This might be a bug in Logview: fontification-functions / jit-lock-function is not supposed to access and modify a large portion of the buffer. I don't use Logview, and you did not give a detailed recipe to reproduce the issue, so it's difficult to give more precise advice.