From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Richard Stallman Newsgroups: gmane.emacs.bugs Subject: bug#57684: locked narrowing breaks existing code without an apparent way to repair Date: Thu, 15 Sep 2022 23:38:15 -0400 Message-ID: References: <2e25ca87e3c6ebb795d7@heytings.org> <87bkrowmiw.fsf@gnus.org> <83y1um3crp.fsf@gnu.org> <83illq2mp4.fsf@gnu.org> Reply-To: rms@gnu.org Content-Type: text/plain; charset=Utf-8 Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="10417"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 57684@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Sep 16 05:39:15 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 1oZ2CB-0002Vo-3T for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 16 Sep 2022 05:39:15 +0200 Original-Received: from localhost ([::1]:52208 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oZ2C9-0001sc-JT for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 15 Sep 2022 23:39:13 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47868) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oZ2By-0001o7-NG for bug-gnu-emacs@gnu.org; Thu, 15 Sep 2022 23:39:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:42007) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oZ2By-0001Wc-9Z for bug-gnu-emacs@gnu.org; Thu, 15 Sep 2022 23:39:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oZ2Bx-0003Ti-OQ for bug-gnu-emacs@gnu.org; Thu, 15 Sep 2022 23:39:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Richard Stallman Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 16 Sep 2022 03:39:01 +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.166329950613323 (code B ref 57684); Fri, 16 Sep 2022 03:39:01 +0000 Original-Received: (at 57684) by debbugs.gnu.org; 16 Sep 2022 03:38:26 +0000 Original-Received: from localhost ([127.0.0.1]:41085 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oZ2BN-0003So-PR for submit@debbugs.gnu.org; Thu, 15 Sep 2022 23:38:26 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:55982) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oZ2BJ-0003SY-K5 for 57684@debbugs.gnu.org; Thu, 15 Sep 2022 23:38:24 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:60020) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oZ2BE-0001Rd-DL for 57684@debbugs.gnu.org; Thu, 15 Sep 2022 23:38:16 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=Date:References:Subject:In-Reply-To:To:From: mime-version; bh=LFcm8VpVGzNjFMg+49N0Z3908JmN4BW5GIcOh+ig2OI=; b=dYMRIJX4AIwq hLykw/hl21D7Kaw6emW5v05zz7LTDJpwoWNX8EHEIXJz/tMzD+zie4kNiSaCq7Q6u6GJAH0ioLn4N Hd+OM7yos4rFcX2Wc4E3CogoTZnuIAX9rVNUBEv+lG7FPihIaqH2ep6pqrV44hr3OvL8xC6Oh+Ozg oEPdw5nOUeohr4YApbAFpc4/BbkAHcKIDPn3Kh3StFR2EDUdk0yGCTuzXL2cG30iJc1SW0pvzQg80 nn1+zUjQtZedtV/xMsppjWMNsYvJCzLiQH623+tENmz2UNy7BTE2tV1YwV2GwcOfvB1c+Qq/ta5BH S5dGhyMzn2zHkUMBsgmT3Q==; Original-Received: from rms by fencepost.gnu.org with local (Exim 4.90_1) (envelope-from ) id 1oZ2BD-0003e5-LZ; Thu, 15 Sep 2022 23:38:15 -0400 In-Reply-To: <83illq2mp4.fsf@gnu.org> (message from Eli Zaretskii on Wed, 14 Sep 2022 14:57:11 +0300) 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:242677 Archived-At: [[[ To any NSA and FBI agents reading my email: please consider ]]] [[[ whether defending the US Constitution against all enemies, ]]] [[[ foreign or domestic, requires you to follow Snowden's example. ]]] > 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? -- Dr Richard Stallman (https://stallman.org) Chief GNUisance of the GNU Project (https://gnu.org) Founder, Free Software Foundation (https://fsf.org) Internet Hall-of-Famer (https://internethalloffame.org)