From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.devel Subject: Re: Tree-sitter maturity Date: Sat, 28 Dec 2024 08:11:08 +0000 Message-ID: <874j2o4483.fsf@localhost> References: <1ed88fca-788a-fe9f-b6c8-edb2f49751c9@mavit.org.uk> <67428b3d.c80a0220.2f3036.adbdSMTPIN_ADDED_BROKEN@mx.google.com> <86ldwdm7xg.fsf@gnu.org> <6765355b.c80a0220.1a6b24.3117SMTPIN_ADDED_BROKEN@mx.google.com> <00554790-CACA-4233-8846-9E091CF1F7AA@gmail.com> <86msgl2red.fsf@gnu.org> <87o710sr7y.fsf@debian-hx90.lan> <8734i9tmze.fsf@posteo.net> <86plldwb7w.fsf@gnu.org> <87bjwx3rok.fsf@localhost> <86wmfkutqb.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24601"; mail-complaints-to="usenet@ciao.gmane.io" Cc: philipk@posteo.net, rms@gnu.org, manphiz@gmail.com, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Dec 28 09:10:22 2024 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 1tRRtu-0006Ew-2f for ged-emacs-devel@m.gmane-mx.org; Sat, 28 Dec 2024 09:10:22 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1tRRtS-0003jW-92; Sat, 28 Dec 2024 03:09:54 -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 1tRRtO-0003jH-Gf for emacs-devel@gnu.org; Sat, 28 Dec 2024 03:09:50 -0500 Original-Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1tRRtM-0005qF-Dn for emacs-devel@gnu.org; Sat, 28 Dec 2024 03:09:50 -0500 Original-Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id A1918240103 for ; Sat, 28 Dec 2024 09:09:45 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1735373385; bh=0vB6YLbPti2XgZa9VNDn8tnUP8XgafpZHDXVGjaCUIE=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: From; b=JjLovl5TouYrFQFLEBR/upewbKHU4dcECTP5wR1YkFQIWIgd4ddxBS7SHmKcfR8r4 0tAgdAgjTocMH9u4t/6mMR2B8vbXArtI0taTxAldpAMmYSMTqQxz0FLfrUK8rF/RQ7 91Ns7YFhiIB0BNk2Q9WEKlvBKHsR6yO6B0L4sxRNtjiUbtbALDJJKBOeZrcDgRGoWs CiJeU7wtrNaHsVA8ZZi9nAyeCq9AARVzhxiCM7X6NzigJa87tlNy9smfldzk6y/4H2 4KcNvZJ1cslSyUNtuWH+VqsJWrcT9YAbuBGfWVPmWNI02yAdUx4+GBpW/AHzpoWxaD cVeiIWNKwhMxA== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4YKw541YrDz6tsb; Sat, 28 Dec 2024 09:09:44 +0100 (CET) In-Reply-To: <86wmfkutqb.fsf@gnu.org> Received-SPF: pass client-ip=185.67.36.66; envelope-from=yantar92@posteo.net; helo=mout02.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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:327240 Archived-At: Eli Zaretskii writes: >> > We could have done that, but there's no way we could keep the value of >> > treesit-language-source-alist up-to-date... >> >> May this list be updated from ELPA? Via a special package or maybe via compat.el. > > Everything is possible, if someone volunteers to do the job. (There's > still the question I asked whether such a package will be useful and > used by enough users, but that is secondary.) To be clear, I mostly wanted to show that keeping the value up to date is not impossible (contrary to your assertion). Whether it is a viable practical option is another question. But the idea should not be rejected outright. > In general, people are suggesting all kinds of semi-solutions for a > problem that has no solution, and isn't ours to solve to begin with. > I don't mind providing such semi-solutions, if someone volunteers, I'm > just pointing out their (almost obvious) downsides, so people would > not make a mistake of thinking we can solve this like we are used to > solve such problems when they are under our complete control. Fair. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at . Support Org development at , or support my work at