From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings Newsgroups: gmane.emacs.bugs Subject: bug#56682: Fix the long lines font locking related slowdowns Date: Sat, 30 Jul 2022 12:05:17 +0000 Message-ID: <65cb7c73fdbb8a1673c5@heytings.org> References: <837d46mjen.fsf@gnu.org> <8a3eaeef01be5bfaa5ef@heytings.org> <05388e8d8812bfa3695d@heytings.org> <83v8rf5894.fsf@gnu.org> <65cb7c73fd4a999cca00@heytings.org> <83k07u6dkm.fsf@gnu.org> <65cb7c73fdceb7548382@heytings.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="35852"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 56682@debbugs.gnu.org, monnier@iro.umontreal.ca To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Jul 30 14:06:28 2022 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1oHlEi-00095w-KC for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 30 Jul 2022 14:06:28 +0200 Original-Received: from localhost ([::1]:60490 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oHlEh-0005Yl-Ky for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 30 Jul 2022 08:06:27 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55282) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oHlEI-0005SG-Ti for bug-gnu-emacs@gnu.org; Sat, 30 Jul 2022 08:06:05 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:44484) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oHlEI-0007KO-Ki for bug-gnu-emacs@gnu.org; Sat, 30 Jul 2022 08:06:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oHlEI-0003aF-5b for bug-gnu-emacs@gnu.org; Sat, 30 Jul 2022 08:06:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Gregory Heytings Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 30 Jul 2022 12:06:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 56682 X-GNU-PR-Package: emacs Original-Received: via spool by 56682-submit@debbugs.gnu.org id=B56682.165918272213716 (code B ref 56682); Sat, 30 Jul 2022 12:06:02 +0000 Original-Received: (at 56682) by debbugs.gnu.org; 30 Jul 2022 12:05:22 +0000 Original-Received: from localhost ([127.0.0.1]:34229 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oHlDd-0003ZA-PH for submit@debbugs.gnu.org; Sat, 30 Jul 2022 08:05:21 -0400 Original-Received: from heytings.org ([95.142.160.155]:59086) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oHlDa-0003Yz-Ec for 56682@debbugs.gnu.org; Sat, 30 Jul 2022 08:05:20 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1659182717; bh=ezvOWjMoBA2ypBBT++J3bysSTIS/8/qTKYmW4Zybqc8=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=AcevFVvQgvH9T6FwUlQaB2wVd3DdKhEULBmJc1Eo96aknqugKN+p2M6VwU5CsMoR6 GJkb4es/2njJ8R/iWs37FQ/xeenQgbJMffBkD4PTIEIBsPRh7IsZOfRW19ts4cLlLF El0JbDo0niNZ5HGCeKv9GBHBovdEEVBnuor8SyAirc8q8wmNBUQ93h5B3ao3D0XOHv /cg6tH507fm6+DW4tFEOK9Q1KYTMrSQJayzXmtgUfJheR8NaxbqMjAFhAAY+/2ZmvA HBV9nYVEKx+uisx8x1k9Oqrzos6dPHveYdQn9atyV3xAOusN6Ot2JoX3QFXf+1R60l nE1Ij/Y4aM0yQ== In-Reply-To: <65cb7c73fdceb7548382@heytings.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:238264 Archived-At: >>> is apparently not enough, because "2-3" seems to install an >>> integer-or-marker-p check on the third argument, which raises a >>> (wrong-type-argument integer-or-marker-p nil) or (wrong-type-argument >>> integer-or-marker-p t) error when narrow-to-region is called from >>> byte-compiled code. >> >> Where's the integer-or-marker-p test installed and/or called from? > > It is called when narrow-to-region, which has its own opcode, is called > from byte-compiled code. But I have no idea where it is installed. > Got it, fixed on master. make bootstrap is probably necessary.