From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings Newsgroups: gmane.emacs.devel Subject: Re: Tree-sitter introduction documentation Date: Thu, 29 Dec 2022 17:00:52 +0000 Message-ID: <86ce08480372e6e5db04@heytings.org> References: <83wn6ri7pn.fsf@gnu.org> <5e0a3185-de82-b339-0fa2-956779e63d6f@cornell.edu> <868rj6vfep.fsf@gmail.com> <4895891b-e5ea-9c37-f51b-df2e479ee758@yandex.ru> <83y1qt11xq.fsf@gnu.org> <9eb013da-d0fc-8e17-c6e3-1e8f913aebfa@yandex.ru> <83pmc50xxc.fsf@gnu.org> <71cfe4e8-3bb8-b0a6-9be5-8c0a6d92cfab@yandex.ru> <83h6xg29z3.fsf@gnu.org> <838ris22n4.fsf@gnu.org> <8335901zz3.fsf@gnu.org> <87cz84y5le.fsf@posteo.net> <3F91FDEA-881A-49DB-BB52-5A0D81C004CE@gmail.com> <87k02aihrz.fsf@posteo.net> <86ce08480352653995b8@heytings.org> <87r0wigqnb.fsf@posteo.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19591"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Yuan Fu , Stefan Monnier , Eli Zaretskii , Dmitry Gutov , Tim Cross , emacs-devel@gnu.org To: Philip Kaludercic Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Dec 29 18:05:49 2022 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 1pAwLl-0004uf-PA for ged-emacs-devel@m.gmane-mx.org; Thu, 29 Dec 2022 18:05:49 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pAwHD-0002DB-TG; Thu, 29 Dec 2022 12:01:07 -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 1pAwH3-000274-5y for emacs-devel@gnu.org; Thu, 29 Dec 2022 12:00:57 -0500 Original-Received: from heytings.org ([95.142.160.155]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pAwH1-0002v8-HD; Thu, 29 Dec 2022 12:00:56 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20220101; t=1672333253; bh=Dtr6KOM/G850Ib4QcyCOpVrdqZPqlb2m7cMr2lCoK6I=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=vW1Lpb+gIzbgI/4JOyT0dXwpCu4Ep5dYmtLt71s7vHvpxJI20nqanhm6WdVPUucyS lX+jhIb02Rd9lkFFpB0KpC33IUDVrCNp3IeAr4/WsOIpB6Hw0wrrCMkO1nz1fDkHoV vo1XZVfYERRsqVVpjSeH//ulnKTuRjAcyTjY1o0wpo5LRFMiLxonBliDcUlpBQe8H9 nNNd4zJjoox09GVH7FEbKtr92Wad/RHidk2ekDimp6+bo/Ysqu7/kQI7ScAw3J51sD p57YLCO2BLCRxAn9UDlk/BCaMgsNsYKoWHVTd6WCdfwn/tVmxChyQ5CaXknXs/YST0 GyCnog1f0MzJg== In-Reply-To: <87r0wigqnb.fsf@posteo.net> Received-SPF: pass client-ip=95.142.160.155; envelope-from=gregory@heytings.org; helo=heytings.org X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 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, 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.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:302046 Archived-At: >> That's not possible, no, at least not without a lot of complications >> that do not seem worth the price, compared to installing Node.js. And >> note that even if that were feasible, it would only solve the first >> half of the problem: to transform a grammar.js file into its >> corresponding parser.c file, you also need the tree-sitter command line >> program. > > Not necessarily, that could also be ported to JavaScript. > I'm puzzled. What would be the benefit of doing that? Installing Node.js and tree-sitter is easy. > > That being said, I don't imagine it to be an easy process. > Indeed. The generator is about 13500 lines of non-trivial Rust code. >> Indeed, grammar authors are not limited to the standard Node.js API, >> they can import other libraries. > > How common is this in practice? Is it encouraged? > I don't know. I'd guess it is not frequent, but neither encouraged nor discouraged.