From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: progmodes/project.el and search paths Date: Wed, 05 Aug 2015 18:08:02 +0300 Message-ID: <83614tu625.fsf@gnu.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> <86io8ucl69.fsf@stephe-leake.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1438787321 24211 80.91.229.3 (5 Aug 2015 15:08:41 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 5 Aug 2015 15:08:41 +0000 (UTC) Cc: emacs-devel@gnu.org To: Stephen Leake Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Aug 05 17:08:33 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 1ZN0Iw-0005Zf-9s for ged-emacs-devel@m.gmane.org; Wed, 05 Aug 2015 17:08:30 +0200 Original-Received: from localhost ([::1]:40867 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZN0Iv-0005AC-H3 for ged-emacs-devel@m.gmane.org; Wed, 05 Aug 2015 11:08:29 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38711) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZN0Ig-0005A4-7W for emacs-devel@gnu.org; Wed, 05 Aug 2015 11:08:15 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZN0Id-0004Ug-2F for emacs-devel@gnu.org; Wed, 05 Aug 2015 11:08:14 -0400 Original-Received: from mtaout25.012.net.il ([80.179.55.181]:60930) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZN0Ic-0004Uc-L8 for emacs-devel@gnu.org; Wed, 05 Aug 2015 11:08:10 -0400 Original-Received: from conversion-daemon.mtaout25.012.net.il by mtaout25.012.net.il (HyperSendmail v2007.08) id <0NSM006006YRCD00@mtaout25.012.net.il> for emacs-devel@gnu.org; Wed, 05 Aug 2015 18:04:14 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout25.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NSM00MNZ772F290@mtaout25.012.net.il>; Wed, 05 Aug 2015 18:04:14 +0300 (IDT) In-reply-to: <86io8ucl69.fsf@stephe-leake.org> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 80.179.55.181 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:188444 Archived-At: > From: Stephen Leake > Date: Wed, 05 Aug 2015 01:18:54 -0500 > > >> 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. If EDE finds this useful, what doubt is there that other Lisp programs will? How many examples do we need before we decide that a specific trait of a project is "useful"? I say one is enough (sometimes more than enough). > 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. That's exactly my problem: I find such an approach surprising, to say the least, when building such basic infrastructure. When you build infrastructure, you don't wait for clients to come requesting basic features. You are supposed to study the use cases and the entities you want to support, and provide support for at least the standard/basic aspects and traits of those entities. I think there should be small doubt that access to project documentation, including its build command, is one of these basics, because every project has that.