From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#57684: locked narrowing breaks existing code without an apparent way to repair Date: Fri, 16 Sep 2022 09:04:28 +0300 Message-ID: <83sfkr4zyr.fsf@gnu.org> References: <2e25ca87e3c6ebb795d7@heytings.org> <87bkrowmiw.fsf@gnus.org> <83y1um3crp.fsf@gnu.org> <83illq2mp4.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6748"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 57684@debbugs.gnu.org To: rms@gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Sep 16 08:05:49 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 1oZ4U0-0001ZV-Nz for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 16 Sep 2022 08:05:48 +0200 Original-Received: from localhost ([::1]:51020 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oZ4Tz-0000m7-J2 for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 16 Sep 2022 02:05:47 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49668) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oZ4TG-0000U8-Ok for bug-gnu-emacs@gnu.org; Fri, 16 Sep 2022 02:05:08 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:42197) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oZ4TG-0005L3-D4 for bug-gnu-emacs@gnu.org; Fri, 16 Sep 2022 02:05:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oZ4TG-0001C8-8D for bug-gnu-emacs@gnu.org; Fri, 16 Sep 2022 02:05:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 16 Sep 2022 06:05:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 57684 X-GNU-PR-Package: emacs Original-Received: via spool by 57684-submit@debbugs.gnu.org id=B57684.16633082854566 (code B ref 57684); Fri, 16 Sep 2022 06:05:02 +0000 Original-Received: (at 57684) by debbugs.gnu.org; 16 Sep 2022 06:04:45 +0000 Original-Received: from localhost ([127.0.0.1]:41275 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oZ4Sy-0001BZ-Ts for submit@debbugs.gnu.org; Fri, 16 Sep 2022 02:04:45 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:38818) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oZ4Sw-0001BM-MK for 57684@debbugs.gnu.org; Fri, 16 Sep 2022 02:04:42 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:50522) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oZ4Sr-0005Jh-HV for 57684@debbugs.gnu.org; Fri, 16 Sep 2022 02:04:37 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=Z2iWIMShR68krk9g6uuXV+UDGobuQNDlaYkvLQXj+jg=; b=PkjOIzFU7sE+ wYLHEASZMS4G1/G8IQoGDkbjGuTFqHBVkogjVwPcPGEqg6TIKDiqPL7Q3QoPH+H8+VdM6ne3LfqL2 TrgRZWL0GA4nXecFxK9kyIsX42fYKcABZz0ltB4QkZK/evQBhzyQi+/6f52ousV8oIBkNvIVu4tvK 5y+vOs60poGAIL6hRTV7iwbI5bKV6A7e07X0NmKjAFKTIrEkB/P35HXdDMZRGr29ur5ueBxTyhWhx ciMue93zQeo3Hzb3jQwblNU/CpXA2Bd65VGd60QTSz9NcFn1nVyKmGDbZA/B6EKkBdGhzRLyWDjbg /exYDVAOZotG4qq9ENSAug==; Original-Received: from [87.69.77.57] (port=2892 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oZ4So-0006PZ-9X; Fri, 16 Sep 2022 02:04:34 -0400 In-Reply-To: (message from Richard Stallman on Thu, 15 Sep 2022 23:38:15 -0400) 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:242695 Archived-At: > From: Richard Stallman > Cc: 57684@debbugs.gnu.org > Date: Thu, 15 Sep 2022 23:38:15 -0400 > > > Even if Elisp code is buggy, Emacs itself should never allow it to fall into an infinite loop and stop > > > responding to C-g, leaving full restart as the only way out. > > It used to be impossible to have an infinite loop in Emacs Lisp that > you could not quit out of. The Lisp interpreter and tye bytecode > interpreter both had calls to QUIT in all the loops of Lisp execution. > Likewise, all the loops in C code that corresponded to Lisp loops, and > might fail to terminate if given circular lists, such as Fmemq, > had calls to QUIT. > > If that is now no longertrue, what made it cease to be true? It is still true. The problem exists only with Lisp code that is run when QUITs are either intentionally disabled, or when Lisp is run from the display engine, where QUIT is caught and basically ignored. The particular case which started this thread is of the latter variety.