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: Tree-sitter introduction documentation Date: Tue, 03 Jan 2023 14:14:05 +0200 Message-ID: <83bknf24tu.fsf@gnu.org> References: <83edszjslp.fsf@gnu.org> <87tu1vxs3a.fsf@ledu-giraud.fr> <831qozjob7.fsf@gnu.org> <87cz8jxoat.fsf@ledu-giraud.fr> <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> <87wn6cyey5.fsf@posteo.net> <787B1EB4-1925-4679-8747-449DCD685432@gmail.com> <83y1qo6h7a.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27583"; mail-complaints-to="usenet@ciao.gmane.io" Cc: casouri@gmail.com, philipk@posteo.net, monnier@iro.umontreal.ca, dgutov@yandex.ru, theophilusx@gmail.com, emacs-devel@gnu.org To: rms@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Jan 03 13:19:03 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 1pCgFz-0006v2-M7 for ged-emacs-devel@m.gmane-mx.org; Tue, 03 Jan 2023 13:19:03 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pCgBC-00029K-T6; Tue, 03 Jan 2023 07:14:06 -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 1pCgBB-000291-Et for emacs-devel@gnu.org; Tue, 03 Jan 2023 07:14:05 -0500 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 1pCgBA-0008Th-5V; Tue, 03 Jan 2023 07:14:04 -0500 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=XzwWjQuDvauekipc0UkfDfZZl6WMSalAE6CpPdvbBk4=; b=odkZZqKpLwPV UEcEf2WzfvF1qtVwk+G0VhvfNKv3dhjBcU3I/dc62P78+p2HNA3oyNHDlS6Vs5bd2CaqZUOAhosoj Jr5FjnpwaNfSbxXr5FpVuyxV5EtHggZf++3pYXacCtUhUDpOgWn3ySAIDaURknCg454csxS9UASbT 3DIm3aJ0P+b3Ja8WItks0rrn19aOXF23hm0Sx5abvgFbOYdD+tJ4MkJw2vPe9lRT9bCMsrkuLmex+ V0yySUEmpWZg83MGt02QsVK/DbwJk4rbRGkvZnY8Mrz9J7T+eL54Diwo5CCAndeaRxk3mfCc3+QY3 +VWaYPZOYPtTxK5r9I3f0g==; Original-Received: from [87.69.77.57] (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 1pCgB2-0005Q0-7C; Tue, 03 Jan 2023 07:13:56 -0500 In-Reply-To: (message from Richard Stallman on Mon, 02 Jan 2023 23:08:11 -0500) 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:302212 Archived-At: > From: Richard Stallman > Cc: casouri@gmail.com, philipk@posteo.net, monnier@iro.umontreal.ca, > dgutov@yandex.ru, theophilusx@gmail.com, emacs-devel@gnu.org > Date: Mon, 02 Jan 2023 23:08:11 -0500 > > > (message "Cloning repository") > > ;; git clone xxx --depth 1 --quiet workdir > > (treesit--call-process-signal > > "git" nil t nil "clone" url "--depth" "1" "--quiet" > > workdir) > > This discussion is about details of code I don't know, so I have not > been following it. However, making it depend specifically on git > raises a concern. In general, we should not do that. > > What job is this part of? Why propose to make it soecifically require > git? What would it be doing with git, here? Clone the repository and then build the library from the sources in that repository. The build itself uses a C/C++ compiler and linker. As I explained in my other message, the ability to build the latest development version of a grammar library seems to be important, given even our relatively short experience, given how these grammar libraries are currently developed and released.