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#61235: 30.0.50; tree-sit: `treesit-node-check' lacks a way to tell if a node belongs to a deleted parser Date: Mon, 06 Feb 2023 16:05:30 +0200 Message-ID: <835yceris5.fsf@gnu.org> References: <83edr3q8ez.fsf@gnu.org> <87o7q7dl4o.fsf@masteringemacs.org> <83a61rq6ck.fsf@gnu.org> <87k00uexdt.fsf@masteringemacs.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="20391"; mail-complaints-to="usenet@ciao.gmane.io" Cc: casouri@gmail.com, 61235@debbugs.gnu.org To: Mickey Petersen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Mon Feb 06 15:06:28 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 1pP28a-000560-4l for geb-bug-gnu-emacs@m.gmane-mx.org; Mon, 06 Feb 2023 15:06:28 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pP28G-0003qV-Lc; Mon, 06 Feb 2023 09:06: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 1pP28A-0003q3-U8 for bug-gnu-emacs@gnu.org; Mon, 06 Feb 2023 09:06:04 -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 1pP28A-0001lB-7b for bug-gnu-emacs@gnu.org; Mon, 06 Feb 2023 09:06:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pP289-0000QX-Me for bug-gnu-emacs@gnu.org; Mon, 06 Feb 2023 09:06:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 06 Feb 2023 14:06:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 61235 X-GNU-PR-Package: emacs Original-Received: via spool by 61235-submit@debbugs.gnu.org id=B61235.16756923331590 (code B ref 61235); Mon, 06 Feb 2023 14:06:01 +0000 Original-Received: (at 61235) by debbugs.gnu.org; 6 Feb 2023 14:05:33 +0000 Original-Received: from localhost ([127.0.0.1]:47650 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pP27h-0000Pa-2o for submit@debbugs.gnu.org; Mon, 06 Feb 2023 09:05:33 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:38536) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pP27e-0000PK-JI for 61235@debbugs.gnu.org; Mon, 06 Feb 2023 09:05:31 -0500 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 1pP27X-0001aN-WE; Mon, 06 Feb 2023 09:05:24 -0500 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=1p4XBNDB76yYfT8IOjyciRxPZ5DlkjtoEWDETxqi7CA=; b=QwR8FDxO+o9Q jP0MxkEjKzmb8eQmMhv0XZHTfmtsRwPSLHtpY9SaGB16DoNg48a8ujLZHmcgcd76ISEeBp0UCiVqQ Yar/mvA2UYeVSLz/RGyv/BYiMRjrRr6XvrP5HDpK0szVOzB3FLgdxRm3cFpL3PURYDL7KGaeIcN0U H/PKd7g4s3vQJi8bgICeC8If8zkGxBGqN9Q7IJmYytxBZrIxnMyTuciW6tr7gUwiKMIwm7z2MG3dC PevSk4IPbXf2iHIJIWqTsu1BCuW6R7iS+cemV7ZayQWuKS1smMUPP3td7LFF0Ym+zdepMo1FAxIWr JNnJnAaaLnHTJ9s0bCMzYA==; 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 1pP27W-0003oZ-3w; Mon, 06 Feb 2023 09:05:23 -0500 In-Reply-To: <87k00uexdt.fsf@masteringemacs.org> (message from Mickey Petersen on Mon, 06 Feb 2023 13:19:57 +0000) 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:254961 Archived-At: > From: Mickey Petersen > Cc: casouri@gmail.com, 61235@debbugs.gnu.org > Date: Mon, 06 Feb 2023 13:19:57 +0000 > > > I'm asking why the Lisp program cannot track the parsers its uses and > > deletes, and instead expects the core to do the janitor's job for it. > > Because I have a proxy-like object of a real node because they're > invalidated if a buffer is edited, even if the parcel of code I hold a > node reference to is untouched. That's just how tree-sitter works, so > I deal with it like this. That part works fine for I can of course use > `treesit-node-check' to determine if it's outdated and thus needs > refreshing (or not.) > > The problems begin when the parser is also, for one reason or another, > destroyed. But it is only destroyed if your program calls treesit-parser-delete, no? Anyway, I'm okay with exposing treesit_check_parser to Lisp, if you really insist. But please be sure you want to insist, because I'm not really convinced.