From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Alan Mackenzie Newsgroups: gmane.emacs.devel Subject: Re: emacs master + org Wrong type argument: number-or-marker-p Date: Tue, 2 Aug 2022 18:59:07 +0000 Message-ID: References: <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> <835yja7o7j.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="39247"; mail-complaints-to="usenet@ciao.gmane.io" Cc: gregory@heytings.org, mattiase@acm.org, philipk@posteo.net, silent2600@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Aug 02 21:02:14 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 1oIx9i-000A16-Rr for ged-emacs-devel@m.gmane-mx.org; Tue, 02 Aug 2022 21:02:14 +0200 Original-Received: from localhost ([::1]:48792 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oIx9h-0003J6-SW for ged-emacs-devel@m.gmane-mx.org; Tue, 02 Aug 2022 15:02:13 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42968) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oIx71-00016c-UY for emacs-devel@gnu.org; Tue, 02 Aug 2022 14:59:27 -0400 Original-Received: from colin.muc.de ([193.149.48.1]:16911 helo=mail.muc.de) by eggs.gnu.org with smtp (Exim 4.90_1) (envelope-from ) id 1oIx6y-0000Un-Bt for emacs-devel@gnu.org; Tue, 02 Aug 2022 14:59:25 -0400 Original-Received: (qmail 90074 invoked by uid 3782); 2 Aug 2022 18:59:08 -0000 Original-Received: from acm.muc.de (p4fe15cce.dip0.t-ipconnect.de [79.225.92.206]) (using STARTTLS) by colin.muc.de (tmda-ofmipd) with ESMTP; Tue, 02 Aug 2022 20:59:07 +0200 Original-Received: (qmail 18293 invoked by uid 1000); 2 Aug 2022 18:59:07 -0000 Content-Disposition: inline In-Reply-To: <835yja7o7j.fsf@gnu.org> X-Submission-Agent: TMDA/1.3.x (Ph3nix) X-Primary-Address: acm@muc.de Received-SPF: pass client-ip=193.149.48.1; envelope-from=acm@muc.de; helo=mail.muc.de X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=unavailable 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:292995 Archived-At: Hello, Eli. On Tue, Aug 02, 2022 at 16:46:24 +0300, Eli Zaretskii wrote: > > Date: Mon, 1 Aug 2022 20:05:44 +0000 > > Cc: Mattias Engdegård , > > Eli Zaretskii , philipk@posteo.net, silent2600@gmail.com, > > emacs-devel@gnu.org > > From: Alan Mackenzie > > I see in > > commit 9d8a6c82838f2f24e76a67379b02956aa668d7cf > > Author: Gregory Heytings > > Date: Mon Aug 1 19:11:01 2022 +0000 > > the following text: > > +Note that, in rare circumstances, Emacs may decide to leave, for > > +performance reasons, the accessible portion of the buffer unchanged > > +after a call to @code{narrow-to-region}. > > You cannot do this. narrow-to-region and widen aren't nice-to-have > > optional extras, they are essential parts of program functionality. If > > you stop them working properly, programs will break. It is a bit like > > the Lisp machine randomly failing to perform some car operations. > This happens only in buffers with very long lines, where we want to > prevent Lisp programs called from low-level facilities, like > redisplay, to scan the entire buffer. So Lisp programs will "only" fail to work in buffers with long lines. I protest at this. There surely could have been a solution to whatever the problem was that respected the integrity of the Lisp machine. There is not even a return code to say that a byte-code instruction has failed to work. Surely there should be an error signalled if such happens, since the program is broken after ignoring an instruction. Ignoring what a programmer programmed cannot be a good strategy. > "Normal" invocations from Lisp will not meet with this. A great deal of pain is fore-ordained. I protest also that this wasn't discussed openly on emacs-devel. > > Would it also be possible to add in some commentry motivating this > > unusual action? > I added some verbiage. Thanks. -- Alan Mackenzie (Nuremberg, Germany).