From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Manuel Giraud Newsgroups: gmane.emacs.devel Subject: Re: [SPAM UNSURE] Maybe we're taking a wrong approach towards tree-sitter Date: Wed, 28 Jul 2021 16:41:01 +0200 Message-ID: <87y29qec1u.fsf@elite.giraud> References: <8735rzyzbz.fsf@163.com> <86v94v3xh9.fsf@stephe-leake.org> <87o8amy88o.fsf@163.com> <20210728123612.pr2ddrf6vmynknxn@Ergus> <877dhawpr7.fsf@163.com> <83mtq6tw7v.fsf@gnu.org> <87eebish4g.fsf@163.com> <83h7getvgi.fsf@gnu.org> <8735rysgmc.fsf@163.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="38783"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (berkeley-unix) Cc: Eli Zaretskii , stephen_leake@stephe-leake.org, spacibba@aol.com, emacs-devel@gnu.org To: Andrei Kuznetsov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Jul 28 16:41:47 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 1m8kkk-0009sp-Ru for ged-emacs-devel@m.gmane-mx.org; Wed, 28 Jul 2021 16:41:46 +0200 Original-Received: from localhost ([::1]:38498 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m8kkj-0003E7-TW for ged-emacs-devel@m.gmane-mx.org; Wed, 28 Jul 2021 10:41:45 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:34300) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m8kk8-0002L6-QU for emacs-devel@gnu.org; Wed, 28 Jul 2021 10:41:08 -0400 Original-Received: from ledu-giraud.fr ([51.159.28.247]:26745) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m8kk6-0000AX-Fk; Wed, 28 Jul 2021 10:41:08 -0400 Original-Received: from elite.giraud ( [10.1.1.1]) by ledu-giraud.fr (OpenSMTPD) with ESMTPSA id eb955385 (TLSv1.3:AEAD-AES256-GCM-SHA384:256:NO); Wed, 28 Jul 2021 16:41:03 +0200 (CEST) In-Reply-To: <8735rysgmc.fsf@163.com> (Andrei Kuznetsov's message of "Wed, 28 Jul 2021 21:38:35 +0800") Received-SPF: pass client-ip=51.159.28.247; envelope-from=manuel@ledu-giraud.fr; helo=ledu-giraud.fr X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-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.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:271747 Archived-At: Andrei Kuznetsov writes: > Eli Zaretskii writes: > >> If you are talking about affecting how TS does lexical analysis for >> some language, then I see no reason why we in the Emacs project would >> want to do that. We don't _want_ to develop parsers if we can use >> parsers available out there. Lexical analysis of a parser is >> determined by the language it parses, so you need only to change the >> parser when the language changes, or to fix a bug. Both are part of >> the job of the TS developers, so there should be no need for us to get >> busy with that. Exactly like we do with other libraries we use that >> aren't developed as part of the Emacs project. > > Okay, thanks for the clarification Yes, thanks for these clarifications and sorry for my misunderstanding. I still have one question left though: will the parsers C code (and TS C code) land into the emacs repo or will TS be accessible as an external library? -- Manuel Giraud