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: [SPAM UNSURE] Maybe we're taking a wrong approach towards tree-sitter Date: Fri, 30 Jul 2021 16:59:29 +0300 Message-ID: <83fsvvrjge.fsf@gnu.org> References: <8735rzyzbz.fsf@163.com> <86v94v3xh9.fsf@stephe-leake.org> <87wnpargnb.fsf@elite.giraud> <87h7gey7zx.fsf@163.com> <83pmv2twrl.fsf@gnu.org> <86sfzwogsn.fsf@stephe-leake.org> <87o8akmy4p.fsf@163.com> <87bl6kezgu.fsf@telefonica.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="9768"; mail-complaints-to="usenet@ciao.gmane.io" Cc: ofv@wanadoo.es, emacs-devel@gnu.org To: Arthur Miller Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jul 30 16:10:19 2021 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 1m9TDP-0002Jh-8v for ged-emacs-devel@m.gmane-mx.org; Fri, 30 Jul 2021 16:10:19 +0200 Original-Received: from localhost ([::1]:41232 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m9TDN-0001ft-AT for ged-emacs-devel@m.gmane-mx.org; Fri, 30 Jul 2021 10:10:17 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36026) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m9T3R-0007Qk-1A for emacs-devel@gnu.org; Fri, 30 Jul 2021 10:00:01 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:39790) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m9T3P-0007C9-Sg; Fri, 30 Jul 2021 09:59:59 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:4502 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 1m9T3N-00031T-J5; Fri, 30 Jul 2021 09:59:59 -0400 In-Reply-To: (message from Arthur Miller on Fri, 30 Jul 2021 15:30:42 +0200) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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" Xref: news.gmane.io gmane.emacs.devel:271848 Archived-At: > From: Arthur Miller > Date: Fri, 30 Jul 2021 15:30:42 +0200 > Cc: emacs-devel@gnu.org > > > and also about > > decreasing the maintenance load. > Sure, but it is also a limitation. If Emacs will rely on TS maintainers > to create new grammars and update existing ones when language changes, > it means Emacs users will have to wait for changes until they are > fixed upstream, similar as how gnu/linux distros work regarding > packaging. We have the same "problem" with every other library we use: the image libraries, GnuTLS, HarfBuzz, etc. Besides, TS is used by quite a few projects, so how long do you think it will take for serious problems in language support to be fixed? OTOH, take a look at some places in Emacs that don't have active maintainers: problems there sometimes take forever to fix. This is what happens when a project wants to control everything in its domain, but lacks manpower for doing so. It is not reasonable to expect Emacs to have experts on board for parsing every language on the face of Earth. It won't work. > I don't know, I am maybe overly sceptical to TS; I don't mean it is a > bad package, and I am sure it has it's place in other editors, I am just > not sure how it fits in Emacs where everything is easily configurable > and extensible. Not everything. Again, take the other optional libraries we use as examples: they cannot be extended inside Emacs.