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#62333: 30.0.50; Issue with tree-sitter syntax tree during certain changes Date: Mon, 27 Mar 2023 20:05:07 +0000 Message-ID: <728618716b5bdf2ef2da@heytings.org> References: <87fs9yur7r.fsf@gmail.com> <83sfduelab.fsf@gnu.org> <8FC25A01-6934-43BB-899C-CA5926BEA3CF@gmail.com> <83jzz5c8ml.fsf@gnu.org> <83edpdc6sn.fsf@gnu.org> <1ca302bf-99dc-7f9e-8544-063064a1cb21@yandex.ru> <831qlcdisi.fsf@gnu.org> <398721ad-79b0-3f6d-97b3-4902d9bfbe39@yandex.ru> <83wn34c2qa.fsf@gnu.org> <3b3d82d1-f0f6-a768-a5db-8dc9386a5a34@yandex.ru> <83r0tcbz8g.fsf@gnu.org> <1967361679760225@umbzx4hqxrw5qxo7.sas.yp-c.yandex.net> <83mt40bxzd.fsf@gnu.org> <83jzz4bugh.fsf@gnu.org> <3d64520c-54da-a04a-ed0d-a66b4e753f8a@yandex.ru> <831qlcaysh.fsf@gnu.org> <29679184-7366-0167-9e94-def97048f663@yandex.ru> <83v8inal29.fsf@gnu.org> <9886ffa5-ead2-50d5-a325-f6704b736ada@yandex.ru> <728618716b8c5349d27e@heytings.org> <83bkke9uue.fsf@gnu.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="24274"; mail-complaints-to="usenet@ciao.gmane.io" Cc: wkirschbaum@gmail.com, casouri@gmail.com, 62333@debbugs.gnu.org, dgutov@yandex.ru To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Mar 27 22:06:23 2023 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 1pgt6k-0005yU-NK for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 27 Mar 2023 22:06:22 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pgt6V-0003ir-R0; Mon, 27 Mar 2023 16:06:07 -0400 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 1pgt6T-0003g8-1u for bug-gnu-emacs@gnu.org; Mon, 27 Mar 2023 16:06:05 -0400 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 1pgt6Q-0005xN-Bo for bug-gnu-emacs@gnu.org; Mon, 27 Mar 2023 16:06:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pgt6P-0001Ww-Q1 for bug-gnu-emacs@gnu.org; Mon, 27 Mar 2023 16:06:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Gregory Heytings Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 27 Mar 2023 20:06:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 62333 X-GNU-PR-Package: emacs Original-Received: via spool by 62333-submit@debbugs.gnu.org id=B62333.16799475115818 (code B ref 62333); Mon, 27 Mar 2023 20:06:01 +0000 Original-Received: (at 62333) by debbugs.gnu.org; 27 Mar 2023 20:05:11 +0000 Original-Received: from localhost ([127.0.0.1]:48504 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pgt5b-0001Vm-A8 for submit@debbugs.gnu.org; Mon, 27 Mar 2023 16:05:11 -0400 Original-Received: from heytings.org ([95.142.160.155]:56706) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pgt5Y-0001Vb-Ry for 62333@debbugs.gnu.org; Mon, 27 Mar 2023 16:05:09 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1679947507; bh=3ULPHliZ87l0pzhI2MR0sczcNLWdkuVxY2V9QPd/alE=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=oEZkdaIwuSA+s5V5ou1ddNH/OIwQDjlg68vesarqyX+kt344oM33IEJjCFRJBUZ+N xRNqRKrNKT/IfK6vI7Yh780+zbqUSaP2AbbJjOCyipo3MLpTzHo6WQgonJKQYk+nsQ +4Ttz/KjIx8MUcTnVK4IS094MxqhHjyZbz1Et1a24yY8CGBic1plEcBDObBcZCVFB3 9xhmCl4GQNlsZSk+pb3riPhMgkjBC183h798myKYIOtwrhb7zy5jHM9urt7JFUBjMt aY3y6kKUNvFPvxiXByn57GXZvYUyWDzTBZWfAf/gAXaKqEr6UXPCB+cdvXHgp550+l nYbJmbbh1llpw== In-Reply-To: <83bkke9uue.fsf@gnu.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-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:258771 Archived-At: >>>>>> Again, I'm talking about using a parser library. We may need to >>>>>> introduce a way of limiting the parser to a certain range of buffer >>>>>> text positions, independently of narrowing. >>>>> >>>>> Except it's already limited by narrowing. >>>> >>>> Which is a fragile, semi-broken means, as we all know. >>> >>> What is a broken mess, is user-level narrowing. And how the downstream >>> code can never guess the purpose the narrowing was applied for. >> >> Note that this is what labeled narrowings attempts to solve. > > Labeled narrowing cannot solve this because it does nothing to alleviate > the problems with user-defined narrowing. So if the user narrows the > buffer, we cannot do anything to safely widen in the general case, and > labeled narrowing cannot help us. > I must be missing something, but I don't understand what you mean. If a user has narrowed a buffer to a certain region A-B, and if we want to limit a parser to a certain region C-D, we can do that safely with (with-narrowing C D :label 'parser-library BODY) which will work, independently of the A-B narrowing set by the user, and will reset the narrowing to A-B upon return. And functions inside BODY will have to use (without-narrowing :label 'parser-library ...) to get access to the whole buffer.