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: Subprojects in project.el (Was: Eglot, project.el, and python virtual environments) Date: Fri, 25 Nov 2022 09:30:00 +0200 Message-ID: <83sfi7v6dj.fsf@gnu.org> References: <87zgcq68zp.fsf@ericabrahamsen.net> <4c5f4b07-3df6-d700-83f8-9a9d1b684afc@yandex.ru> <84781346-5b88-2be5-38bb-02696fcf1364@yandex.ru> <87o7t2vj19.fsf@dfreeman.email> <877czqtyfy.fsf@dfreeman.email> <87zgcml7g7.fsf@gmail.com> <2ba04533-097a-a1da-ff3f-2c9506fd488e@yandex.ru> <875yf9bbzb.fsf@gmail.com> <87wn7oa0aw.fsf@gmail.com> <7a5b76fd-fb15-8c1e-ea29-bf11f7e0d2ae@yandex.ru> <87bkoya815.fsf@gmail.com> <0024a67d-b8e5-b35c-1b22-82541a170eb3@yandex.ru> <871qptai4d.fsf_-_@gmail.com> <83o7swyipe.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="25225"; mail-complaints-to="usenet@ciao.gmane.io" Cc: joaotavora@gmail.com, monnier@iro.umontreal.ca, danny@dfreeman.email, eric@ericabrahamsen.net, emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Nov 25 08:30:13 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 1oyTA3-0006ID-N0 for ged-emacs-devel@m.gmane-mx.org; Fri, 25 Nov 2022 08:30:11 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oyT9b-0000xz-69; Fri, 25 Nov 2022 02:29:43 -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 1oyT9Z-0000xq-Gc for emacs-devel@gnu.org; Fri, 25 Nov 2022 02:29:41 -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 1oyT9Y-0000dP-FY; Fri, 25 Nov 2022 02:29:40 -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=HV8+BL7iWisemJPC0poreSTE1HMXBEgssUo0Oe9ioLs=; b=MITsjQfdxpFF 40q3qOqLoohsiHMZ5RlB6gEirXsuAhQxQRJ0Gm5UwU4DD66slIi51jO9kszyut7fipEo4d22dsuoq olN8oB52FBEUMFr87hynZeR6S/3uPJtLw3i5+IMKtZGcCCvwYGaKeK3D+RLOGA0fM+NpNv/n+tf27 YvaRObwQ9ith2Sn4Y9afe2fR+5I5BdxKTvY5LSe+QJiklJM629iRVoWOLqw6SOgAz1PZq3eahXvP5 Fs9nHAA5U/CXPg99kKOk4XTisiQuY3vEvQvpSzVHrW8xI/26/uZP0L6GC40yyrhqZ2T3WkDTMBgm+ K/+Ht8Qbs1A5K6qskQ5Z9Q==; 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 1oyT9X-0001HN-Jy; Fri, 25 Nov 2022 02:29:40 -0500 In-Reply-To: (message from Dmitry Gutov on Fri, 25 Nov 2022 00:11:29 +0200) 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:300467 Archived-At: > Date: Fri, 25 Nov 2022 00:11:29 +0200 > Cc: monnier@iro.umontreal.ca, danny@dfreeman.email, eric@ericabrahamsen.net, > emacs-devel@gnu.org > From: Dmitry Gutov > > > Is this okay for code outside project.el to know the internal structure of a > > project object in general, and in particular cons "by hand" a 'transient' > > project object? I thought this was a closely-guarded implementation detail > > that even doc strings are not allowed to divulge? > > Joao's code here is not production-ready, but it wasn't intended as such > either, I guess. > > Any 'sub-projects' function would likely be generic with implementations > belonging to a particular backend. And a backend knows how to construct > its instances. I'm probably missing something: how does a Lisp program construct an instance of a project with a known backend? For example, if the project is of the 'transient' kind, how would such a Lisp program go about constructing an instance without exposing/knowing about the internals of the project object? I see no generic make-project API that such a Lisp program could call. What did I miss?