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.devel Subject: Re: Update on tree-sitter structure navigation Date: Sat, 09 Sep 2023 20:28:35 +0300 Message-ID: <83edj7tfwc.fsf@gnu.org> References: <5E7F2A94-4377-45C0-8541-7F59F3B54BA1@gmail.com> <8a5b3b3e-f091-3f38-09d4-c4e26bec97f9@yandex.ru> <83h6o5xj4f.fsf@gnu.org> <83sf7nvov3.fsf@gnu.org> <580010af-7328-768d-b1c2-d80d7099a290@yandex.ru> <83a5tvvaoo.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="31117"; mail-complaints-to="usenet@ciao.gmane.io" Cc: casouri@gmail.com, emacs-devel@gnu.org, danny@dfreeman.email, theo@thornhill.no, jostein@secure.kjonigsen.net, dev@rjt.dev, wkirschbaum@gmail.com, pedz@easesoftware.com To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Sep 09 19:29:34 2023 Return-path: Envelope-to: ged-emacs-devel@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 1qf1m1-0007tn-Sq for ged-emacs-devel@m.gmane-mx.org; Sat, 09 Sep 2023 19:29:34 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qf1lG-0004zQ-Vk; Sat, 09 Sep 2023 13:28:47 -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 1qf1lF-0004z0-1F for emacs-devel@gnu.org; Sat, 09 Sep 2023 13:28:45 -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 1qf1lC-00052S-MG; Sat, 09 Sep 2023 13:28:42 -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=KHp7xBySA0ECSxfNF5aIy2H8k3zbQU7PO3WHczfknyE=; b=mmbcvlzfCdAk O8WPPuehknPL3t+d2MFNckgmiPJAMm7kxHOhsocT6d/XT0WM2loBx6gkv3HcmisKjxZgwY2bRFijI m+KmGxSqxDzkbtXkgbGwg1ROLy+JX5T1zqxP0ieoDpufR8fnU2J3Dj1/0fGKsTuXY9N2oJ+HznnVl jOseUAiq4+wFOAuUGv0qiktm4hX42x3CqWJZk+Hh5/8TBiof8wN+WA1ZbYFFiELdX9OC8unsAJP74 F8wBH3SWPqW2FOJMTk9tt6NWooWLwiHep2C0Vch2onl3X4NH0nu5MBZXyl+5WZ2FXINgizYQdSvky CDjQbsM/GjxixL0TV6BbKw==; In-Reply-To: (message from Dmitry Gutov on Sat, 9 Sep 2023 20:04:07 +0300) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:310418 Archived-At: > Date: Sat, 9 Sep 2023 20:04:07 +0300 > Cc: casouri@gmail.com, emacs-devel@gnu.org, danny@dfreeman.email, > theo@thornhill.no, jostein@secure.kjonigsen.net, dev@rjt.dev, > wkirschbaum@gmail.com, pedz@easesoftware.com > From: Dmitry Gutov > > > How is it useful to ask users to use, say, 2-year old versions of > > grammar libraries, especially for languages where either the language > > or the library (or both) change quickly? > > It would be better to use a 2-year-old grammar which works with our mode > than a new grammar which breaks our mode anyway. But worse than using a 6-month-old grammar that doesn't break the mode and has a lot of improvements. > > How is it friendlier to downgrade to an older version (which would > > require fetching it, building it with a C compiler, and installing it) > > than to patch a single Lisp file? Actually, people don't even need to > > patch their Emacs installations, they could instead have a fixed > > version of the Lisp file in their home directories or in site-lisp. > > So we'll suggest they manually copy the latest version of xxx-js-mode.el > from master over to their site-lisp? That will be our recommendation in > case a grammar breaks? Something like that, yes. Or applying the diffs from the fix. > I suppose we could publish all ts grammars in "core ELPA". Yes, that could be a good solution, if nothing better comes up.