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 19:16:22 +0300 Message-ID: <83y4hpsobt.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> <55C1DA6F.1000209@yandex.ru> <83zj25sqsl.fsf@gnu.org> <55C22C57.9070307@yandex.ru> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1438791416 1982 80.91.229.3 (5 Aug 2015 16:16:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 5 Aug 2015 16:16:56 +0000 (UTC) Cc: emacs-devel@gnu.org, deng@randomsample.de, eric@siege-engine.com To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Aug 05 18:16:44 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 1ZN1Mw-0002Ua-Ed for ged-emacs-devel@m.gmane.org; Wed, 05 Aug 2015 18:16:42 +0200 Original-Received: from localhost ([::1]:41168 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZN1Mu-0005Wk-ML for ged-emacs-devel@m.gmane.org; Wed, 05 Aug 2015 12:16:40 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57690) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZN1Mq-0005WU-BK for emacs-devel@gnu.org; Wed, 05 Aug 2015 12:16:37 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZN1Ml-0004Lm-KK for emacs-devel@gnu.org; Wed, 05 Aug 2015 12:16:36 -0400 Original-Received: from mtaout24.012.net.il ([80.179.55.180]:48364) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZN1Ml-0004Ld-77 for emacs-devel@gnu.org; Wed, 05 Aug 2015 12:16:31 -0400 Original-Received: from conversion-daemon.mtaout24.012.net.il by mtaout24.012.net.il (HyperSendmail v2007.08) id <0NSM00N00A1I6300@mtaout24.012.net.il> for emacs-devel@gnu.org; Wed, 05 Aug 2015 19:08:06 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout24.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NSM00MARA5IG010@mtaout24.012.net.il>; Wed, 05 Aug 2015 19:08:06 +0300 (IDT) In-reply-to: <55C22C57.9070307@yandex.ru> 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.180 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:188451 Archived-At: > Cc: deng@randomsample.de, eric@siege-engine.com, emacs-devel@gnu.org > From: Dmitry Gutov > Date: Wed, 5 Aug 2015 18:31:35 +0300 > > On 08/05/2015 06:23 PM, Eli Zaretskii wrote: > > > Again, sounds silly, given how most, if not all, modern build tools > > work. > > That is counter to my experience. The modern build tools work in a > variety of different ways. You mean, some of them don't support specifying how to build documentation? Which ones? > > But (shrug) not a catastrophe: the corresponding attribute will simply > > be nil, or the command to build everything. > > And I don't understand what you mean here. An attribute can exist even if with some projects its value will be nil or a trivial "build-all" command. IOW, even if some projects won't have any non-trivial value for this attribute, it's not an argument against the attribute's existence. > > IOW, I see no problem here, and no reasons to consider this unfit for > > the API. > > It's fit. As soon as we're sure someone is going to write a Lisp program > making use of this part of the API. And by "sure", I mean we have at > least a proof-of-concept patch for a non-trivial piece of functionality. I don't think it's correct to wait for specific requests for every single sub-feature, when developing infrastructure like this one. Some basic traits should be supported just because they are basic, before someone asks. > > I don't think you have this luxury when you work on infrastructure. > > I don't think anyone here has the authority to tell me what to spend > time on. I didn't tell you anything except my views on this. > > E.g., company.el is "not very interesting" for me, but I still try > > very hard to fix every issue in the display engine that you or your > > users report. > > You don't work on adding new features to it, however. Yes, I do. But that's besides the point, isn't it? > > Yes. They are both no-brainers to have in the infrastructure that > > AFAIU you are trying to provide. It might even be much more useful to > > a Lisp program that only cares about the manual of a project. > > It makes sense to go for features with bigger impact first. If this is just a matter of priority, I'm okay with whatever the decision is. I was under the impression that the mere need is being questioned.