From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: emacs master + org Wrong type argument: number-or-marker-p Date: Wed, 03 Aug 2022 16:47:17 -0400 Message-ID: References: <83tu6v27yh.fsf@gnu.org> <6F871C02-AC26-4B89-B64B-E9F4ACACDBE7@acm.org> <83sfmf26b6.fsf@gnu.org> <835yja7o7j.fsf@gnu.org> <83v8ra5uee.fsf@gnu.org> <87wnbqcebn.fsf@yahoo.com> <83o7x259wg.fsf@gnu.org> <87edxyc5ds.fsf@yahoo.com> <83iln95yd7.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19561"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: Po Lu , acm@muc.de, 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 Wed Aug 03 22:48:28 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 1oJLI4-0004tI-Ig for ged-emacs-devel@m.gmane-mx.org; Wed, 03 Aug 2022 22:48:28 +0200 Original-Received: from localhost ([::1]:50076 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oJLI3-0001jL-DA for ged-emacs-devel@m.gmane-mx.org; Wed, 03 Aug 2022 16:48:27 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42692) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oJLHB-00012B-VL for emacs-devel@gnu.org; Wed, 03 Aug 2022 16:47:33 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:42657) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oJLH8-000622-CD; Wed, 03 Aug 2022 16:47:31 -0400 Original-Received: from pmg1.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id 77044100189; Wed, 3 Aug 2022 16:47:28 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg1.iro.umontreal.ca (Proxmox) with ESMTP id D9A451000F3; Wed, 3 Aug 2022 16:47:26 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1659559646; bh=fA4m9smDuH2WsOl45uIpeLil2LSMEuSSq4PD7in+zKE=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=ps59CKYtpLIM/h4DfwilFLoHmmVzRCEf3ptnfTj+1+KfJ3pV89l8r7RR5wS+OmY3e 0zc40YIgl/xDGmweeFd1oMGNMavRJ3yaUvdCA6kl2GFrHfncJSaIXX8CmbydYxXi/3 zE+7oTBnNs73NXzwx9d3wCvtYXIADTKoSdG9178MCtAtdRuahQpEWhfFyfb9CLaRi8 frVf4YYqVAFq0LwAJoSsWfahx8yPgt+AshlzqIvYZY4E71x7JRlS6EL5nQrHImfgnX u35WInBPqNgOicSUt4iBmEmSflo3FvXItBgjr5GydulZbXRQVNRKv8g5qAJOZt/J9z uPxm5CfP8gnag== Original-Received: from milanesa (unknown [46.44.221.102]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 7C757120377; Wed, 3 Aug 2022 16:47:25 -0400 (EDT) In-Reply-To: <83iln95yd7.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 03 Aug 2022 15:02:12 +0300") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham 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:293030 Archived-At: >> Then wouldn't it be better to fix the font-locking code to not widen >> outside bounds explictly specified by redisplay, instead of making >> `widen' and `narrow-to-region' in effect inoperable in those >> circumstances? > How would that work in practice? Font-locking code uses functions and > regexps provided by the major modes, so it cannot by itself prevent > widening. I don't understand what you're talking about. AFAIK in 99% of the cases, font-lock.el itself widens, then uses the regexps (which can't widen) and the functions provided by the major mode almost none of which (with rare exceptions, of course, most of them historical) will widen since font-lock already did it for them (and since widening will lead to bugs when used within something like mmm-mode or mhtml-mode). I don't see much need to "prevent widening". Stefan