From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Paul Pogonyshev 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 16:47:29 +0200 Message-ID: References: <87pmfx6h7y.fsf@gnus.org> <2b58b8f5429a6e3aecda@heytings.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000cf133705e8b853ea" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="32074"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Lars Ingebrigtsen , 57804@debbugs.gnu.org To: Gregory Heytings Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Sep 15 16:48:39 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 1oYqAQ-00088h-7h for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 15 Sep 2022 16:48:38 +0200 Original-Received: from localhost ([::1]:58634 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oYqAP-0002s5-4m for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 15 Sep 2022 10:48:37 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:41644) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oYq9q-0002qX-OO for bug-gnu-emacs@gnu.org; Thu, 15 Sep 2022 10:48:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:41925) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oYq9q-00037N-GW for bug-gnu-emacs@gnu.org; Thu, 15 Sep 2022 10:48:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oYq9q-0003pI-4A for bug-gnu-emacs@gnu.org; Thu, 15 Sep 2022 10:48:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Paul Pogonyshev Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 15 Sep 2022 14:48:02 +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.166325327214657 (code B ref 57804); Thu, 15 Sep 2022 14:48:02 +0000 Original-Received: (at 57804) by debbugs.gnu.org; 15 Sep 2022 14:47:52 +0000 Original-Received: from localhost ([127.0.0.1]:58857 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oYq9f-0003oH-HF for submit@debbugs.gnu.org; Thu, 15 Sep 2022 10:47:52 -0400 Original-Received: from mail-ej1-f52.google.com ([209.85.218.52]:39708) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oYq9c-0003me-6T for 57804@debbugs.gnu.org; Thu, 15 Sep 2022 10:47:50 -0400 Original-Received: by mail-ej1-f52.google.com with SMTP id y17so37669502ejo.6 for <57804@debbugs.gnu.org>; Thu, 15 Sep 2022 07:47:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date; bh=Q1k5U7DqID+LEOJxlZ0+s/0AIIo82DgdYhs8gER2XRk=; b=Z5EShc2d1TDvuu90YoMvYo8fno7fPQBXSmccJeuEfnz+9e49/hntwZnPAsqttyEK7y WKenLTZpPrcOLlZPkzZoqf/Uw3cqlhAMA7ZxWotg8jKeLi/H9VirouFzJLMpsYXG+EpB 4Q8agMZZuuiJcbp7kinP0bzDhWoQrTwRu6JF7yWOO4kbb4R7SOSdoKPb5cJYZ+ZlJyFD pOkopYo0yOn2WYGRTvcco/udQoXZJWEjGOuLixqoHJEd0WGWtR3YGB8fsXRFce8cL7Be W1UQc/CDptu4HvNH/SIa+AKneULS6n+ln4dKc5j9HNh8kcINY0UdTr9aGW2FXQXZY2GA 4Ilw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date; bh=Q1k5U7DqID+LEOJxlZ0+s/0AIIo82DgdYhs8gER2XRk=; b=dfk2rq9i04Y1R5ZJW9bfN0skhWUg3KiwxoCzzOVlW4956q5NQ+Gde4mxuMS0lk5GZ0 Lna5xmptj9Ec/6MhFt9tko1kukBZJQYkz1Ie9V5LtvHJ/6IcbpMW3+D1UE39VERaHKc2 MOAk69nsj4qFugUbPdfQk3r3/TpYiHy0mOoXYvytRz40znUrXWhbN8XEDA48FOA4YM8E K2sW5u/QYe4EVx1elLW23maYnLFeOWr7fg+pNaG+QlkoNCu+haxw8XxJ0XyLdG7Lrpt+ VD5SpJ09WKfSLfN3dphZQTHskzFTHecynQNq2BxJ7FK54r9UVCfbZlLZ1f0BlflQic66 fXPQ== X-Gm-Message-State: ACrzQf0V10NV7vTNi4TFosu192bNyBkXpiCZyIlT85dEnVPwj6mXgYug kI7rtMHQq/sIH592o0m/pJlF2TzhbaYsOB3U/g== X-Google-Smtp-Source: AMsMyM7NCUTW87P7/evNx4FjTviMn7dUjdKirY8DT9QA+R+bVF0+MzvVEfUPrpEDbnfJRdETs9yCab1TBwGCaWVimH0= X-Received: by 2002:a17:907:b09:b0:76f:99cc:81cd with SMTP id h9-20020a1709070b0900b0076f99cc81cdmr235647ejl.530.1663253261258; Thu, 15 Sep 2022 07:47:41 -0700 (PDT) In-Reply-To: <2b58b8f5429a6e3aecda@heytings.org> 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:242596 Archived-At: --000000000000cf133705e8b853ea Content-Type: text/plain; charset="UTF-8" > Logview will have to be adapted to deal with the > possibility of a locked narrowing. Is it technically impossible to lift narrowing restrictions in Emacs 29 (as in, something would break), or is it "you have to rewrite, because we have decided so"? Paul On Wed, 14 Sept 2022 at 19:34, Gregory Heytings wrote: > > > > > E.g. in my case this happened in Logview mode, because it expected > > `widen' to, well, widen, but Emacs `master' introduced half-cooked > > narrowed locking that broke that expectation > > > > Yes, master contains work in progress. If you want stable code, you > should use the release branch. > > Note that the "fully cooked" narrowing will not magically solve that > problem, though. Logview will have to be adapted to deal with the > possibility of a locked narrowing. What you should most probably do in > your case is to increase the value of long-line-threshold (or disable > whatever causes Logview to infloop when locked narrowing is in effect, if > that's feasible). > --000000000000cf133705e8b853ea Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
> Logview will have to be adapted to deal with the
&= gt; possibility of a locked narrowing.

Is it technic= ally impossible to lift narrowing restrictions
in Emacs 29 (as in= , something would break), or is it "you
have to rewrite, bec= ause we have decided so"?

Paul
On Wed, 1= 4 Sept 2022 at 19:34, Gregory Heytings <gregory@heytings.org> wrote:

>
> E.g. in my case this happened in Logview mode, because it expected > `widen' to, well, widen, but Emacs `master' introduced half-co= oked
> narrowed locking that broke that expectation
>

Yes, master contains work in progress.=C2=A0 If you want stable code, you <= br> should use the release branch.

Note that the "fully cooked" narrowing will not magically solve t= hat
problem, though.=C2=A0 Logview will have to be adapted to deal with the possibility of a locked narrowing.=C2=A0 What you should most probably do i= n
your case is to increase the value of long-line-threshold (or disable
whatever causes Logview to infloop when locked narrowing is in effect, if <= br> that's feasible).
--000000000000cf133705e8b853ea--