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.bugs Subject: bug#62333: 30.0.50; Issue with tree-sitter syntax tree during certain changes Date: Fri, 31 Mar 2023 09:22:55 +0300 Message-ID: <83v8ih30e8.fsf@gnu.org> References: <87fs9yur7r.fsf@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> <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> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6477"; mail-complaints-to="usenet@ciao.gmane.io" Cc: wkirschbaum@gmail.com, gregory@heytings.org, casouri@gmail.com, 62333@debbugs.gnu.org To: Dmitry Gutov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Mar 31 08:23:33 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 1pi8Ae-0001TV-Qh for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 31 Mar 2023 08:23:32 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pi8AK-0007Pj-OL; Fri, 31 Mar 2023 02:23:12 -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 1pi8AB-0007PG-4q for bug-gnu-emacs@gnu.org; Fri, 31 Mar 2023 02:23:03 -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 1pi8AA-00028Q-KD for bug-gnu-emacs@gnu.org; Fri, 31 Mar 2023 02:23:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pi8AA-0002Tl-GE for bug-gnu-emacs@gnu.org; Fri, 31 Mar 2023 02:23:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 31 Mar 2023 06:23:02 +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.16802437729498 (code B ref 62333); Fri, 31 Mar 2023 06:23:02 +0000 Original-Received: (at 62333) by debbugs.gnu.org; 31 Mar 2023 06:22:52 +0000 Original-Received: from localhost ([127.0.0.1]:60182 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pi89z-0002T7-SF for submit@debbugs.gnu.org; Fri, 31 Mar 2023 02:22:52 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:46498) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pi89x-0002Su-NU for 62333@debbugs.gnu.org; Fri, 31 Mar 2023 02:22:50 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pi89s-00027b-1E; Fri, 31 Mar 2023 02:22:44 -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=zFNDrxnzxdQ+NrSMrgcfU5Evq88PHIfZ1mhv4Qnmdw8=; b=MteC0x5B4+Et qm7Cx3//j3fPU4o+3HlQY8LiZA6UuPzw5vJthG5RXI5tPSot/z2M7vuHcJ+y7VoU8Bi02Ah9cj0UB X5KnKCExKf5XQ7c3NuU52CR8aGg5WrVsDjfCB5lkArRB0DSoHFh2xHU2npzireLg9nPxGPs+yzTT4 6jDoPir2aE/be2DSWcN+Dau3C7ztCNeoT858neP9Cb58TtL/NGB4ljanyb7g07y20N7GyAWGxPX8l omOS2pOF6QxULgyRdhl/zj3E8EGY+vk13X4bBXPXCJHCMpO2iPLMWOoTwX+G2bf7PypJVLEWJN0mV HjjWigo0auOYilEx1rpWAA==; Original-Received: from [87.69.77.57] (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 1pi89r-00066h-Ey; Fri, 31 Mar 2023 02:22:43 -0400 In-Reply-To: (message from Dmitry Gutov on Fri, 31 Mar 2023 04:25:41 +0300) 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:258969 Archived-At: > Date: Fri, 31 Mar 2023 04:25:41 +0300 > Cc: wkirschbaum@gmail.com, casouri@gmail.com, 62333@debbugs.gnu.org > From: Dmitry Gutov > > On 30/03/2023 19:04, Eli Zaretskii wrote: > >> Date: Thu, 30 Mar 2023 15:50:31 +0000 > >> From: Gregory Heytings > >> cc: Dmitry Gutov , wkirschbaum@gmail.com, casouri@gmail.com, > >> 62333@debbugs.gnu.org > >> > >>> No, the idea is to create the parser with these restrictions to begin > >>> with. > >> > >> Could you perhaps explain, with some fictitious code, what kind of > >> solution you imagine? I'm not sure I understand (euphemism for: I'm sure > >> I don't understand) the problem statement. > > > > Something like > > > > (treesit-make-parser LANGUAGE BUFFER nil START END) > > What kind of code would be calling this? > > What happens when the user types a character before START? What happens > when they delete a character at START or END? Or a whole line? > > > and > > > > (treesit-parser-set-included-ranges RANGES...) > > > > (the latter already exists). > > Indeed, a way to do this using tree-sitter indeed already exists, > offloading the parsing of the regions to tree-sitter. OTOH, this way we > only get tree-sitter features sorted into regions (parse tree, > indentation, highlighting). > > Whatever other Lisp-level features we wanted to behave differently > between regions, we'd have do implement them the old way. > > >> In what way would the restrictions you have in mind be different from > >> those of a regular narrowing? > > > > User-defined narrowing will never contradict parser restrictions. > > IOW, user-defined narrowing should be only for visual purposes, as > described in another email. And perhaps to restrict movement (which is > related: you can't move to where you can't see). I'm sorry, I cannot afford a discussion where you decided up front you disagree, and just keep looking for arguments in favor of your disagreement. Such discussions are a waste of our time, and I have very little of it to waste. So I won't be responding to any further messages here, unless they ask informative questions where I think I can contribute something useful.