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#64391: buffer narrowing slowdown regression in emacs 29 Date: Sat, 08 Jul 2023 20:58:44 +0000 Message-ID: <239e2a5aa11924a2f1d3@heytings.org> References: <87r0psb51z.fsf@ust.hk> <0AD15A09-F669-48C0-AF5C-971D52F5BF8E@gmail.com> <83v8f3q1ff.fsf@gnu.org> <50A46AAC-2089-45CB-A355-CCB2B4EA8D76@gmail.com> <5995c9ed6a0b39c3070c@heytings.org> <83a5wak1tr.fsf@gnu.org> <26cee506f708f3c6cfe1@heytings.org> <26cee506f70bbc9de58b@heytings.org> <83h6qghpdc.fsf@gnu.org> <26cee506f77e9c87e325@heytings.org> <06A8380F-08A6-464E-9946-02F8498031EC@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="37772"; mail-complaints-to="usenet@ciao.gmane.io" Cc: acohen@ust.hk, 64391@debbugs.gnu.org, mattias.engdegard@gmail.com, eliz@gnu.org To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Jul 08 22:59:11 2023 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 1qIF1L-0009eI-0K for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 08 Jul 2023 22:59:11 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qIF1E-0004dp-0m; Sat, 08 Jul 2023 16:59:05 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qIF1C-0004dP-Fq for bug-gnu-emacs@gnu.org; Sat, 08 Jul 2023 16:59:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1qIF1C-00081O-7Y for bug-gnu-emacs@gnu.org; Sat, 08 Jul 2023 16:59:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1qIF1B-00061M-UW; Sat, 08 Jul 2023 16:59:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Gregory Heytings Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org, bugs@gnus.org Resent-Date: Sat, 08 Jul 2023 20:59:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 64391 X-GNU-PR-Package: emacs,gnus X-Debbugs-Original-Cc: acohen@ust.hk, 64391@debbugs.gnu.org, mattias.engdegard@gmail.com, eliz@gnu.org, bugs@gnus.org Original-Received: via spool by 64391-submit@debbugs.gnu.org id=B64391.168884992823111 (code B ref 64391); Sat, 08 Jul 2023 20:59:01 +0000 Original-Received: (at 64391) by debbugs.gnu.org; 8 Jul 2023 20:58:48 +0000 Original-Received: from localhost ([127.0.0.1]:45272 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qIF0y-00060h-HO for submit@debbugs.gnu.org; Sat, 08 Jul 2023 16:58:48 -0400 Original-Received: from heytings.org ([95.142.160.155]:46492) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1qIF0w-00060P-0V for 64391@debbugs.gnu.org; Sat, 08 Jul 2023 16:58:46 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1688849924; bh=0Huepbc6VUzp1DPFUaZQb9FERcTh5KXmgAUwzMYNK7A=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=vN5XnnHPnWg+BQrwViyH3CxjtqHdKY18/QhZfmL7zQmnOchz4N2W8zjGk90X3FiDF ZUyZt34gpm5IgzfEdC76j1GU6cka2LuZey/q+BnBUnMyyFwxgqahfbz5Bw72cQ1Yg7 z5qoMCZ26+/Js8M6OAXiuh2Jq2bfUM8D6CavucBG8fPSYGHI+0iavRujway4MxiIhX rMSpfWXzr7pDC1eQwSy6sRvdWPpXtDb3P/kqDpq88HDUourrDc3+9ynxa0sChz9ts4 VRUzRbaJB9n6atBTAxDXZo2a+EKP9F+oeluVyvBoi4Dvm/fM36ze8pU7itt0oUwo59 k1AzFJSsINpTQ== 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-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:264797 Archived-At: >> I'm sorry, I don't understand your question. The only way (except by >> using internal functions) to enter a labeled restriction is to use the >> with-restriction special form with its optional label argument. > > Nitpick: it's not a special form, it's a macro. There's a *big* > difference because adding a special form requires changing > `macroexpand-all`, the compiler, yadayada, and it introduces backward > incompatibilities with packages doing their own code-walks. > TIL. I thought that "special form" and "macro" were more or less synonyms. The manual describes lambda, prog2, setq-default, dlet, letrec, named-let, with-suppressed-warnings, with-no-warnings, with-restriction and without-restriction as "special forms", although they are in fact macros. That being said, from a Elisp programmer viewpoint, special forms and macros are similar, and AFAIU one could say that a special form is a macro written in C, and a macro is a special form written in Elisp. Should the above occurrences of "special form" be corrected in the manuals? >> Indeed, but I'd say it's clear enough from the context that "symbol" >> means a quoted symbol here. > > Other nitpick: nil can also be quoted :-) > I knew someone would say that ;-) > > BTW, "LABEL is a symbol" sends the wrong message (a quoted symbol > evaluates to a symbol but it's not itself a symbol). IOW the docstring > should clarify that LABEL is an expression that's evaluated at runtime > (and should return a symbol). While I'm here, is it important that LABEL > evaluates to a symbol? Or is it like `catch/throw` where we expect most > uses to use a symbol but where any other (non-nil) value works as well? > The latter: it's like catch/throw, it's intended to use with a symbol but it could be any non-nil value. So one could write something similar to what is found in the docstring of catch: "LABEL is evalled to get the label to use, it must not be nil".