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: Thu, 30 Mar 2023 22:08:10 +0000 Message-ID: References: <87fs9yur7r.fsf@gmail.com> <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> <83fs9q9vak.fsf@gnu.org> <10aa98b6-908b-c467-7c77-767906692088@yandex.ru> <83h6u585si.fsf@gnu.org> <5c683b3b-48e8-5099-8ab1-459c348d1f88@yandex.ru> <83jzyz7qmy.fsf@gnu.org> <83h6u2444x.fsf@gnu.org> <83edp642h8.fsf@gnu.org> <83bkka3zd9.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="2071"; 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 Fri Mar 31 00:09:22 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 1pi0SP-0000GG-Bd for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 31 Mar 2023 00:09:21 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pi0S8-0003Dn-Kn; Thu, 30 Mar 2023 18:09:04 -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 1pi0S6-0003DK-Fc for bug-gnu-emacs@gnu.org; Thu, 30 Mar 2023 18:09:02 -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 1pi0S6-0006fe-89 for bug-gnu-emacs@gnu.org; Thu, 30 Mar 2023 18:09:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pi0S5-0001O9-MT for bug-gnu-emacs@gnu.org; Thu, 30 Mar 2023 18:09: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: Thu, 30 Mar 2023 22:09: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.16802140965259 (code B ref 62333); Thu, 30 Mar 2023 22:09:01 +0000 Original-Received: (at 62333) by debbugs.gnu.org; 30 Mar 2023 22:08:16 +0000 Original-Received: from localhost ([127.0.0.1]:59669 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pi0RL-0001Ml-IA for submit@debbugs.gnu.org; Thu, 30 Mar 2023 18:08:15 -0400 Original-Received: from heytings.org ([95.142.160.155]:60918) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pi0RJ-0001Mb-Ej for 62333@debbugs.gnu.org; Thu, 30 Mar 2023 18:08:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1680214091; bh=2iCdGPiySgmHZCNgp2g01YjbVRrtkYuxnkfWV7rHaeA=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=cA3DH/TL5tfwRi5hTTbOEV/zBFXbbwi9BgaTig0xExmFs06gSW/yXvU5AepuWs6Op CDVTCJodHW9VdAoskUaWIOiU3FPLS5O5F2QqCFb5KD1l24uW/t48L6qlyq6Gw2F7/o 8bBhu/GTpIhVPAfu17zsvvy9Kp6jw/lONBcogWHoRQA7Hqo4xOTfCLyXZ1pkI2ROn4 XNXLATUZC8UNj16i39m7CswJaawPTvQ1w33WG6WDohzamjm3qtM3uJC9YFWOKYkhIU Nz65Uzyw5MHzW7tB1xW8QBlUYP4q5udskoTV8QCS9K+sfvnqFweJiL/RBei+0Oiu1n qqW2vzZdgvkQA== 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:258951 Archived-At: >>>> The parsers _can_ have access to those ranges, if they need it for >>>> some reason. In general, everything in Emacs should honor the >>>> current restriction, unless there's a good reason to ignore it. >>> >>> Okay, so in the above example by default the parsers will only have >>> access to 1000-1100 for the first one, and 1100-1200 for the second >>> one until the user removes the restrictions. Unless they need to >>> widen the buffer for some (good) reason. >>> >>> If they do widen, will the parsers get access to [400..1100] and >>> [1100..1500], or to the whole buffer? >> >> The former. > > Okay, thanks. Now I think I understand what you want. I'll think about > it. > Two other questions: Should there exist a mechanism to give the parsers access to the whole buffer (IOW, to let them ignore both the bounds passed to 'treesit-make-parser' and the restriction set by the user)? And of course, the bounds given to 'treesit-make-parser' should become markers, right, that is, their position should change whenever the buffer contents change, right?