From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?utf-8?Q?Mattias_Engdeg=C3=A5rd?= Newsgroups: gmane.emacs.devel Subject: Re: emacs master + org Wrong type argument: number-or-marker-p Date: Mon, 1 Aug 2022 20:47:04 +0200 Message-ID: References: <83bkt42ifq.fsf@gnu.org> <87a68ovw0b.fsf@posteo.net> <835yjc2c6f.fsf@gnu.org> <8335eg2ao9.fsf@gnu.org> <875yjbexde.fsf@posteo.net> <83zggn2a0c.fsf@gnu.org> <03AF0800-5252-429C-86BC-85DF9DF449F9@acm.org> <83tu6v27yh.fsf@gnu.org> <6F871C02-AC26-4B89-B64B-E9F4ACACDBE7@acm.org> <83sfmf26b6.fsf@gnu.org> Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.120.0.1.13\)) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="37360"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , philipk@posteo.net, silent2600@gmail.com, emacs-devel@gnu.org To: Gregory Heytings Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Aug 01 20:53:00 2022 Return-path: Envelope-to: ged-emacs-devel@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 1oIaXD-0009Tc-2q for ged-emacs-devel@m.gmane-mx.org; Mon, 01 Aug 2022 20:52:59 +0200 Original-Received: from localhost ([::1]:40680 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oIaXB-0001Nl-Ac for ged-emacs-devel@m.gmane-mx.org; Mon, 01 Aug 2022 14:52:57 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:54802) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oIaRj-0007ld-5u for emacs-devel@gnu.org; Mon, 01 Aug 2022 14:47:23 -0400 Original-Received: from mail212c50.megamailservers.eu ([91.136.10.222]:48850 helo=mail194c50.megamailservers.eu) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oIaRg-0005TW-PH; Mon, 01 Aug 2022 14:47:18 -0400 X-Authenticated-User: mattiase@bredband.net DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=megamailservers.eu; s=maildub; t=1659379631; bh=CXB41Mh/UDER01XkTaJNRmedbVz0Km5x7dXVN6/RQl8=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=aeqM6tYwLI4SV7fB0rFvPwCc5m1bJHadhGryHn11nFpzCxVCzyoY8oGamWAcSWMd/ kaUUkB6pCLHWwyticy3SWQPF8EXR+ic2qDsxYODn0ELhdG8Nqi1r9OEph4r+XCtNku l35HfG02TYkhA40O93IQvQclt6TbK5fznwSCu9zI= Feedback-ID: mattiase@acm.or Original-Received: from smtpclient.apple (c188-150.188-179.bredband.tele2.se [188.150.188.179] (may be forged)) (authenticated bits=0) by mail194c50.megamailservers.eu (8.14.9/8.13.1) with ESMTP id 271Il4T1127817; Mon, 1 Aug 2022 18:47:09 +0000 In-Reply-To: X-Mailer: Apple Mail (2.3654.120.0.1.13) X-CTCH-RefID: str=0001.0A782F17.62E81FAF.0018, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown X-CTCH-Score: 0.000 X-CTCH-Flags: 0 X-CTCH-ScoreCust: 0.000 X-Origin-Country: SE Received-SPF: softfail client-ip=91.136.10.222; envelope-from=mattiase@acm.org; helo=mail194c50.megamailservers.eu X-Spam_score_int: -11 X-Spam_score: -1.2 X-Spam_bar: - X-Spam_report: (-1.2 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:292961 Archived-At: 1 aug. 2022 kl. 20.06 skrev Gregory Heytings : > Is it not allowed to specbind in a function and to unbind in its = caller? No, functions must be balanced with respect to the specbind stack. The = bytecode machinery assumes this to be the case. If you want a special behaviour for narrow-to-region over a dynamic = extent, just bind a dynamic variable. Or, if that is insufficient, write = a new function for it that takes a body function as argument which is = called with the necessary clean-up done afterwards. Or implement it as a = Lisp macro. So please revert all changes relating to the new narrow-to-region = argument and submit a new patch. It's better than somehow trying to = patch up the current unworkable approach.