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: Thu, 04 Aug 2022 10:58:56 +0300 Message-ID: <837d3o4eyn.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> <83iln95yd7.fsf@gnu.org> <83o7x04kul.fsf@gnu.org> <87tu6sa5uf.fsf@yahoo.com> <83czdg4h7p.fsf@gnu.org> <87k07oa2ie.fsf@yahoo.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27259"; mail-complaints-to="usenet@ciao.gmane.io" Cc: monnier@iro.umontreal.ca, 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 Thu Aug 04 10:12:53 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 1oJVyO-0006tG-LF for ged-emacs-devel@m.gmane-mx.org; Thu, 04 Aug 2022 10:12:52 +0200 Original-Received: from localhost ([::1]:57058 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oJVyM-00026g-Va for ged-emacs-devel@m.gmane-mx.org; Thu, 04 Aug 2022 04:12:51 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:44300) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oJVl7-0001ht-UK for emacs-devel@gnu.org; Thu, 04 Aug 2022 03:59:11 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:35732) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oJVl3-00087b-S6; Thu, 04 Aug 2022 03:59:05 -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=LLS9WjVjW+Au+S16jdoCGhOZ57sZd1fvmXpQAWkkqoM=; b=FiiklxPZWnkU O1EuNExJEQ2BkNxAV0HFOmv8r2VsC09EKOeT5gC40fKXA6SiQsSFdKMLah4cJ1KqNlBkQwOXc/Xxc vjyDG0/3S80IUjWF7zLWuD/vwBDamYUfpI+JTB2nxsyS8ABiO1DtF11WbizFZLVPjI947I6mRmaoD J3oYjbxnH6g0NUbpYu9MVLOsEgVkLY1EHo8dy5z8+s7HLwXhzrVX0mEf9hVDumG9fRCvS83O3knMH RykGGGJL1HDo+WF7ZWpN3DyIN4EgfHISovFckviwmmazknfV132xv+rVGq6a6Dmw+JvM2npFrEJK7 ozrIuKa/j19lCSxWSFenNA==; Original-Received: from [87.69.77.57] (port=1738 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 1oJVkz-0003Am-LV; Thu, 04 Aug 2022 03:59:05 -0400 In-Reply-To: <87k07oa2ie.fsf@yahoo.com> (message from Po Lu on Thu, 04 Aug 2022 15:31:21 +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:293045 Archived-At: > From: Po Lu > Cc: monnier@iro.umontreal.ca, acm@muc.de, gregory@heytings.org, > mattiase@acm.org, philipk@posteo.net, silent2600@gmail.com, > emacs-devel@gnu.org > Date: Thu, 04 Aug 2022 15:31:21 +0800 > > > Modes do what they want, and in some cases we have hard time even > > convincing the mode developers that they should try to avoid doing > > that. > > Then maybe we should not impose our opinion of what narrowing is best on > major mode developers? We decided that we do want to impose our opinion, because not doing so results in Emacs being unusable, which is a long-standing gripe of our users. > Forcing restrictions on user code never works. fontification-functions are not user code. > Sooner or later, developers will start performing fontification in a > timer, in order to widen past the "locked narrowing". Long-running timer functions, if they are not interruptible, are a clear bug in the package that does such things, so any such timers will come back as a boomerang to those developers.