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.devel Subject: Re: emacs master + org Wrong type argument: number-or-marker-p Date: Tue, 02 Aug 2022 16:46:24 +0300 Message-ID: <835yja7o7j.fsf@gnu.org> References: <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 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="39824"; 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: Alan Mackenzie Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Aug 02 15:50: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 1oIsHY-000ABV-D1 for ged-emacs-devel@m.gmane-mx.org; Tue, 02 Aug 2022 15:50:00 +0200 Original-Received: from localhost ([::1]:36638 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oIsHX-0002A7-Ad for ged-emacs-devel@m.gmane-mx.org; Tue, 02 Aug 2022 09:49:59 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38466) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oIsEG-0008Ot-0I for emacs-devel@gnu.org; Tue, 02 Aug 2022 09:46:36 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:44734) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oIsEE-0004Ca-9V; Tue, 02 Aug 2022 09:46:34 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=Cu+GjqPP63fXm6taMg43+aD7gxeMsgN2zZLsinHPc7c=; b=KNuPIbj8GpOvzNzjjc1T pNuy3SegK2XiI3Muad7hwGH2CyNS15C/tdC+Q54uJSWiPxKjwh+tU5kdnoXfVIYk1sUjlYY1lbvvw Qp8bw7UAcOT6oVJ4mZMfXCrl3R9P+Ii2CfhF9ZB+qwc95nbr9SHlNo0wTfF0AaFExflisfJOumUbc cagcaKSZjoJk4AI2auBNWXEooZE1ZGNX+kzk3P5BiTcnmiyzGdin3OZIsPN+gPoJVRw7TZCfW48Z7 jnWmVZsBX9YG8NIPMrB6tiY8K+ktris9shpevuM01kjp6KvLsT2i3gMXj4qBMBJIL+YTiwdRnl81o JONLVyjZEY3OKQ==; Original-Received: from [87.69.77.57] (port=1291 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 1oIsED-0003j1-OP; Tue, 02 Aug 2022 09:46:34 -0400 In-Reply-To: (message from Alan Mackenzie on Mon, 1 Aug 2022 20:05:44 +0000) 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:292991 Archived-At: > 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. "Normal" invocations from Lisp will not meet with this. > Would it also be possible to add in some commentry motivating this > unusual action? I added some verbiage.