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: locked narrowing Date: Fri, 02 Dec 2022 00:24:00 +0000 Message-ID: <20f32a53dc3f5fbc5b65@heytings.org> References: <97049541-f5b4-ed3b-b8de-7c0bdc86f0f5@yandex.ru> <6e305c9b-7702-133a-3347-f64db05ade3f@yandex.ru> <83mt89kt10.fsf@gnu.org> <834juglesn.fsf@gnu.org> <83r0xkjw5s.fsf@gnu.org> <83pmd3ioxx.fsf@gnu.org> <47153506021498df087c@heytings.org> <83bkomhlmn.fsf@gnu.org> <4715350602cf2ec6860b@heytings.org> <83a646hkat.fsf@gnu.org> <47153506028bbb3bc8b3@heytings.org> <47153506021115866615@heytings.org> Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="8688"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 56682@debbugs.gnu.org, Eli Zaretskii , dgutov@yandex.ru To: Stefan Monnier Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Dec 02 01:25:20 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 1p0trk-00021y-3N for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 02 Dec 2022 01:25:20 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1p0trY-0000bN-1X; Thu, 01 Dec 2022 19:25:08 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1p0trS-0000b2-KR for bug-gnu-emacs@gnu.org; Thu, 01 Dec 2022 19:25:03 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1p0trS-0004Dj-Bv for bug-gnu-emacs@gnu.org; Thu, 01 Dec 2022 19:25:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1p0trS-0003ik-5E for bug-gnu-emacs@gnu.org; Thu, 01 Dec 2022 19:25:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Gregory Heytings Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 02 Dec 2022 00:25: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.166994064714289 (code B ref 56682); Fri, 02 Dec 2022 00:25:02 +0000 Original-Received: (at 56682) by debbugs.gnu.org; 2 Dec 2022 00:24:07 +0000 Original-Received: from localhost ([127.0.0.1]:42819 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1p0tqZ-0003iP-1H for submit@debbugs.gnu.org; Thu, 01 Dec 2022 19:24:07 -0500 Original-Received: from heytings.org ([95.142.160.155]:40012) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1p0tqU-0003i2-5m for 56682@debbugs.gnu.org; Thu, 01 Dec 2022 19:24:05 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1669940640; bh=NaF5AI7VuK6kwwW3jmR1VWlOzC5QYwCZUSAnxBCIHUo=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=Go8XulJnW2/tpdZ4B3aB0YtmnUs2jNri38yeh3xKBO+QEmITofG7AdfatsfQJdpyb cefKGaFHFkaUuvo68/rxU44U9hFwp09ElsagFWmdV+s3sjILtDMG/bO04WJYeFQ9IE Am20uwvLYrdRwvzXKsXTQF4u5AK9gusAbX4BAAYKs3aR8CtEw3bZws8CL7szPGfsu+ uVDsvOKYj5SS5TbIAGMX8RMdQeXJF40BKuyGy7npfIwBLRxMZZrRIOlWL7BO01k2xN a28LcC7m+SVJoMSlr0CBp8OxquWRRnk/5FID6DTcUh5wTK8vsnKR4oGa73kCYR61F+ DN55pmPPv0H/w== In-Reply-To: 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-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:249681 Archived-At: > > Maybe another option is to do the scan more lazily, keeping track more > precisely of what was scanned and/or needs rescanning. > Thanks. It's an option indeed, the problem here is how to keep track of what was scanned or needs rescanning. I think doing that would probably need two markers for each buffer, say beg_scan_marker and end_scan_marker. An initial scan would set beg_scan_marker to Z and end_scan_marker to BEG. Then each operation in insdel.c would move beg_scan_marker downwards (if the buffer position at which the operation takes place is before the current value of beg_scan_marker) and end_scan_marker upwards (if the buffer position at which the operation takes place is after the current value of beg_scan_marker). Then we would only need to scan beg_scan_marker - some_constant .. end_scan_marker + some_constant again. That being said, I'm not sure the added complexity, to avoid small delays when performing large editing operations in huge buffers, is worth the price.