From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.bugs Subject: bug#62333: 30.0.50; Issue with tree-sitter syntax tree during certain changes Date: Fri, 31 Mar 2023 04:25:41 +0300 Message-ID: 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> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="29211"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Cc: wkirschbaum@gmail.com, casouri@gmail.com, 62333@debbugs.gnu.org To: Eli Zaretskii , Gregory Heytings Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Mar 31 03:26:25 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 1pi3X6-0007QC-Ce for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 31 Mar 2023 03:26:24 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pi3Wn-0001pi-KN; Thu, 30 Mar 2023 21:26:05 -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 1pi3Wk-0001nA-S6 for bug-gnu-emacs@gnu.org; Thu, 30 Mar 2023 21:26: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 1pi3Wk-0002qW-JI for bug-gnu-emacs@gnu.org; Thu, 30 Mar 2023 21:26:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pi3Wj-00036X-TF for bug-gnu-emacs@gnu.org; Thu, 30 Mar 2023 21:26:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Dmitry Gutov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 31 Mar 2023 01:26: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.168022595211918 (code B ref 62333); Fri, 31 Mar 2023 01:26:01 +0000 Original-Received: (at 62333) by debbugs.gnu.org; 31 Mar 2023 01:25:52 +0000 Original-Received: from localhost ([127.0.0.1]:59899 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pi3WZ-00036A-LP for submit@debbugs.gnu.org; Thu, 30 Mar 2023 21:25:52 -0400 Original-Received: from mail-wr1-f52.google.com ([209.85.221.52]:44582) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pi3WW-00035t-Sv for 62333@debbugs.gnu.org; Thu, 30 Mar 2023 21:25:49 -0400 Original-Received: by mail-wr1-f52.google.com with SMTP id d17so20867336wrb.11 for <62333@debbugs.gnu.org>; Thu, 30 Mar 2023 18:25:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1680225943; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :sender:from:to:cc:subject:date:message-id:reply-to; bh=3RMbmvruHaznWI0NNgeR9cUeSCJNSXeBJO9u95tDNHY=; b=eRbccqZjTXqzO8wrvw7uYMcR6jV1/LtXgd6AVj6jMR+hr35i53yqQuuFW3tVVNBv6b e9Cef1pyCz8e7exqhRZ1jDhnHcyzJ/rvcp5cLSYeqd9F1OzrsAJlaexghMx++0tmUBkE 2Kh6/CzK3/uZ8meMJfveN+68iRIrZ1tBqNYDfA2AXE0klYxG/on/gcL5wTHBG7TteAL9 3ue4pxYEv0vImdQQzh38bRmdQtoxCuV68xM6qo7lyUxqX3ssxdBJvPRoW+b0SPiuywSX kgnIQ9JiGZi0Z7bkVXlrjgjnEnXa8DipROdC7nTt7zJs/T6ZzGoV9hRmTzfmFkOsvGSA DkPQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680225943; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :sender:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=3RMbmvruHaznWI0NNgeR9cUeSCJNSXeBJO9u95tDNHY=; b=418yIFMmXW9YPlVw4kM6Bt4tvpfRGwGcFYtfonNBRC02wm9SKJzJK8lrp/qeNscmNy wrSjJjyPR+5w5gGCl/bWU6LPDviTaIoE76ds54Q+pI+/HL2q/3o6vmPjf0xixYr9si47 jBrHryUHKTEBVZtavYtkqNBujJd39f0GqO/oiP8bYphpuELXHe5ncxAn+xtcow2jh3TU 7WsNwlElY1oHH1eCALdAfGlNQeTz5Wrn02qswGqj86Q2Hg+WDliXBWV2/XLdA3WqsZhS lMyM+u0ABvKEbVELVYxwB8pTBa1QLKfRH1FnKSMG5auLyPrdva1wDrLsyQSN/Dd+hL2u lW1w== X-Gm-Message-State: AAQBX9e8j9DUhUjcVaTgfCtMZQk8FWAvCym6WdXG6/eOdBtps3w9MiyM CBTnNA7meGComyRgBzArBBo= X-Google-Smtp-Source: AKy350b7LX/vgAK1maElZadfHoPgAFN5kEsZbPrP6EjfCovxCiWAbmIOKK1r0w9DNpsWfQ0uumEfmg== X-Received: by 2002:a5d:62c6:0:b0:2e4:d939:11b9 with SMTP id o6-20020a5d62c6000000b002e4d93911b9mr2832926wrv.48.1680225943147; Thu, 30 Mar 2023 18:25:43 -0700 (PDT) Original-Received: from [192.168.1.2] ([31.216.80.60]) by smtp.googlemail.com with ESMTPSA id e38-20020a5d5966000000b002d78a96cf5fsm744298wri.70.2023.03.30.18.25.42 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 30 Mar 2023 18:25:42 -0700 (PDT) Content-Language: en-US In-Reply-To: <83h6u2444x.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:258956 Archived-At: 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).