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 api Date: Fri, 01 Apr 2022 20:59:14 +0300 Message-ID: <83v8vs4rd9.fsf@gnu.org> References: <9C5A86D6-0E7D-4DDF-B211-278EF9AC7E01@gmail.com> <87a6gq5mxl.fsf@gmail.com> <877dbu5mgj.fsf@gmail.com> <0BB906F7-BD3A-41CC-9783-19AA16934497@gmail.com> <83pmplq9f3.fsf@gnu.org> <5B304D80-2969-4F59-9A90-412D0A284912@gmail.com> <83ilvbpsvl.fsf@gnu.org> <4A6F417A-EF74-40B6-9517-6C0947AB87A6@gmail.com> <83wnjmiork.fsf@gnu.org> <6D1CD758-2C6F-4843-9739-F2A5D5591648@gmail.com> <67183EAB-5D98-4211-B71B-4618D6266A15@gmail.com> <83lews90ft.fsf@gnu.org> <8D3019A6-83EE-42AB-ADFA-7DA6EBB179B3@gmail.com> <83r16h5npi.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="1444"; mail-complaints-to="usenet@ciao.gmane.io" Cc: larsi@gnus.org, yoavm448@gmail.com, ubolonton@gmail.com, emacs-devel@gnu.org To: Yuan Fu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Apr 01 19:59:36 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 1naLYe-0000Fz-Aq for ged-emacs-devel@m.gmane-mx.org; Fri, 01 Apr 2022 19:59:36 +0200 Original-Received: from localhost ([::1]:43600 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1naLYc-0005Pl-Tf for ged-emacs-devel@m.gmane-mx.org; Fri, 01 Apr 2022 13:59:34 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:52856) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1naLY6-0004j0-Ju for emacs-devel@gnu.org; Fri, 01 Apr 2022 13:59:02 -0400 Original-Received: from [2001:470:142:3::e] (port=35150 helo=fencepost.gnu.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1naLY6-0007u4-8I; Fri, 01 Apr 2022 13:59:02 -0400 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=0fhMeqAFR151TZfV6kmHEgUyp8kpcGxVmKFRFhocHys=; b=Suo8u0pn833T IU5ZbtaqQcQBLdcNUNBDrKE45pHs8+dbaoRe1srWHFSGPaaAdMbrd1Pa5LbsotXxUPuLVJhdpb1/Q qda7wHqu9BfnwA8LRE68fDPNmHyt+nzvgPP3qUIe+cnKdv+u4MNmIT7pwGxjg7oeyMVz1IfpZDtvc Fwmo2xyH/h/68Yy7lrUZu74bCkC4yQDMXnyc1Irp0NdIXYVAMnVtg5rGBainz2qyaoOrA/2IWVtue 0Ym6e7kLWIayyq+lHPA9l/M3C5jIjRIaut5VE1dXfJfWmUJjJF4K7MumJQjCOZW/7LBsZpiPZVvPs egPY4wwn0nrAIGAnGTaOpA==; Original-Received: from [87.69.77.57] (port=3842 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 1naLY5-0006CB-NO; Fri, 01 Apr 2022 13:59:02 -0400 In-Reply-To: (message from Yuan Fu on Fri, 1 Apr 2022 09:48:09 -0700) 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" Xref: news.gmane.io gmane.emacs.devel:287681 Archived-At: > From: Yuan Fu > Date: Fri, 1 Apr 2022 09:48:09 -0700 > Cc: Lars Ingebrigtsen , > Yoav Marco , > Emacs developers , > ubolonton@gmail.com > > >>> If so, I think we should have our own load-path for these > >>> libraries; relying on the standard LD_LIBRARY_PATH etc. is not good > >>> enough (although we should support that as well). I envision that at > >>> least in some cases users will not want to have these libraries in the > >>> public places, or maybe even won't have the requisite access rights to > >>> do so. We should provide Emacs-style alternatives, like some > >>> subdirectory of ~/.emacs.d/ and/or under ${prefix}/lib/ (similar to > >>> *.eln files). > >> > >> Anyone have thoughts on this? > > > > What kind of thoughts? Whether or not to provide this feature (I > > think we should), or how best to implement that? Or something else? > > Thoughts on what paths should we use, whether we want to allow for custom load-paths (I think we should), and if so, the name for the load path variable ({tree-sitter/treesit/...}-language-definition-load-path?) I thought I answered all those questions, with the single exception of the name of the path variable.