From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stephen Leake Newsgroups: gmane.emacs.devel Subject: Re: progmodes/project.el and search paths Date: Wed, 05 Aug 2015 01:18:54 -0500 Message-ID: <86io8ucl69.fsf@stephe-leake.org> References: <55BE209F.1000009@siege-engine.com> <55BE509B.2080307@yandex.ru> <87r3nkjxby.fsf@isaac.fritz.box> <55BF7619.1050701@yandex.ru> <87mvy8jvlh.fsf@isaac.fritz.box> <55BF8522.4010009@yandex.ru> <87lhdsys13.fsf@isaac.fritz.box> <55BFF764.2030002@yandex.ru> <83mvy7tbit.fsf@gnu.org> <55C0FEEB.7040500@yandex.ru> <83h9oeudfs.fsf@gnu.org> <55C1074E.90103@yandex.ru> <83d1z2uach.fsf@gnu.org> <55C11D54.9090105@yandex.ru> <83bnemtpop.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1438755570 31087 80.91.229.3 (5 Aug 2015 06:19:30 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 5 Aug 2015 06:19:30 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Aug 05 08:19:15 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1ZMs2k-0005m6-LY for ged-emacs-devel@m.gmane.org; Wed, 05 Aug 2015 08:19:14 +0200 Original-Received: from localhost ([::1]:39244 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZMs2j-0004sH-VS for ged-emacs-devel@m.gmane.org; Wed, 05 Aug 2015 02:19:13 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52857) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZMs2g-0004sB-BW for emacs-devel@gnu.org; Wed, 05 Aug 2015 02:19:11 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZMs2c-0001gn-MV for emacs-devel@gnu.org; Wed, 05 Aug 2015 02:19:10 -0400 Original-Received: from gproxy1-pub.mail.unifiedlayer.com ([69.89.25.95]:39412) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1ZMs2c-0001fd-Ev for emacs-devel@gnu.org; Wed, 05 Aug 2015 02:19:06 -0400 Original-Received: (qmail 5033 invoked by uid 0); 5 Aug 2015 06:19:03 -0000 Original-Received: from unknown (HELO cmgw3) (10.0.90.84) by gproxy1.mail.unifiedlayer.com with SMTP; 5 Aug 2015 06:19:03 -0000 Original-Received: from host114.hostmonster.com ([74.220.207.114]) by cmgw3 with id 10Jz1r00d2UdiVW010K2yC; Wed, 05 Aug 2015 06:19:02 -0600 X-Authority-Analysis: v=2.1 cv=Qc314Krv c=1 sm=1 tr=0 a=CQdxDb2CKd3SRg4I0/XZPQ==:117 a=CQdxDb2CKd3SRg4I0/XZPQ==:17 a=DsvgjBjRAAAA:8 a=f5113yIGAAAA:8 a=9i_RQKNPAAAA:8 a=y7kgw_RnJtkA:10 a=hEr_IkYJT6EA:10 a=x_XPkuGwIRMA:10 a=uRRa74qj2VoA:10 a=mDV3o1hIAAAA:8 a=dMuJOXMfAAAA:8 a=vaJtXVxTAAAA:8 a=I02jvSOqNapZTjENrj0A:9 Original-Received: from [76.218.37.33] (port=55436 helo=TAKVER2) by host114.hostmonster.com with esmtpa (Exim 4.84) (envelope-from ) id 1ZMs2W-0001q3-7e for emacs-devel@gnu.org; Wed, 05 Aug 2015 00:19:00 -0600 In-Reply-To: <83bnemtpop.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 05 Aug 2015 05:49:26 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (windows-nt) X-Identified-User: {2442:host114.hostmonster.com:stephele:stephe-leake.org} {sentby:smtp auth 76.218.37.33 authed with stephen_leake@stephe-leake.org} X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 69.89.25.95 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:188425 Archived-At: Eli Zaretskii writes: >> Cc: deng@randomsample.de, eric@siege-engine.com, emacs-devel@gnu.org >> From: Dmitry Gutov >> Date: Tue, 4 Aug 2015 23:15:16 +0300 >> >> > E.g., there are a couple of standard ways to specify in a Makefile the >> > directories where the project's files live. Other significant parts >> > of a project's information in a Makefile are recipes to build the >> > project, to install/uninstall it, to clean the tree, etc. Also, >> > various standard commands, like compilation command, link command, a >> > command that creates a library and a manual, etc. >> > >> > These are all clear candidates for "project information an interested >> > Lisp program would like to extract", no? >> >> I can't easily answer that. What's the use for "command that creates a >> manual" (even setting aside the fact that not all projects have that)? >> Calling it in M-x project-create-manual, a command that only does that >> one thing? > > Yes, for starters. Building the whole project from scratch, including > the manuals, is another. Finding out whether the project _has_ a > manual building instructions is yet another. > >> Not very interesting, IMHO. > > I don't understand this criterion. I think the criterion should be > "is this useful". Apparently EDE has the notion of "targets" for this sort of thing. So the EDE users find it useful, for actually running the targets. The question for project.el is whether is would be useful for _other_ (non-EDE) elisp programs; we already have EDE to create and run the targets. I can imagine a full-blown Configuration Management application (think IBM ClearCase) that manages the created binaries as well as the sources; it would want a list of the targets of a project, to ensure they were tracked in the CM database. But such a thing would probably not be written on top of project.el; it would be more like a new EDE project type, or a complete replacement for EDE. Short of that, I can't think of a non-EDE elisp program that would want to know about targets. There might be one someday; we can extend project.el then. There are probably other features in EDE that some non-EDE programs would want to know about; I'm still learning about EDE. -- -- Stephe