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: Wed, 03 Aug 2022 15:02:12 +0300 Message-ID: <83iln95yd7.fsf@gnu.org> 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> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="9058"; mail-complaints-to="usenet@ciao.gmane.io" Cc: acm@muc.de, gregory@heytings.org, mattiase@acm.org, philipk@posteo.net, silent2600@gmail.com, emacs-devel@gnu.org To: Po Lu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Aug 03 14:05:35 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 1oJD83-0002An-3m for ged-emacs-devel@m.gmane-mx.org; Wed, 03 Aug 2022 14:05:35 +0200 Original-Received: from localhost ([::1]:60888 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oJD81-00078g-QJ for ged-emacs-devel@m.gmane-mx.org; Wed, 03 Aug 2022 08:05:33 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56712) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oJD4v-0005az-FN for emacs-devel@gnu.org; Wed, 03 Aug 2022 08:02:21 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:41260) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oJD4t-00027Z-PC; Wed, 03 Aug 2022 08:02:19 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=sxERC9aXx3ZnNBvIU2IYUsiN+xUwaZZ79cDQYRW6h+I=; b=cFdoK23FbjHf BXIGVutKkmf8uAz2Yz9yREQGmemPyJIpDKYJatIkpK06k+9wtHeI55EjlGuZZ0/FpItD2+Y87KnF+ OiCLq1m982vjAw2R+/9I1wxQH9CNuFDqp1naXirSYVhJxc/gPXV915Vj8QA6tQIZuiL8O2idfYJ1P 0eEFqPmoFRRDFbh7KpBNvXUWnsIdQKRWJIY2aTsQbLa4AogoA7dhFqB3Xd7MYBSgHlGi6BZTDbUBR vHZNVpo7njMUBdgfKLQxQIcTG0EqgvL32J9nfN3/8AIq0fRG23FDpECkKEggFlbZC3AtdjeSrGE+h N5TqdFn3XU3GnvZJSrqztw==; Original-Received: from [87.69.77.57] (port=3828 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 1oJD4t-0000Gj-7h; Wed, 03 Aug 2022 08:02:19 -0400 In-Reply-To: <87edxyc5ds.fsf@yahoo.com> (message from Po Lu on Wed, 03 Aug 2022 12:34:07 +0800) 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:293013 Archived-At: > From: Po Lu > Cc: acm@muc.de, gregory@heytings.org, mattiase@acm.org, > philipk@posteo.net, silent2600@gmail.com, emacs-devel@gnu.org > Date: Wed, 03 Aug 2022 12:34:07 +0800 > > Eli Zaretskii writes: > > > It isn't a hypothetical problem. You can try the examples posted here > > yourself, after disabling the feature. Try it once with and then > > without font-lock, and draw your own conclusions. > > 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. Many major modes want their fontification to start from the beginning of the line, which can be very far in a buffer with long lines; and quite a few major modes use code that widens to BOB. What can font-lock do to prevent that?