From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Jorgen Schaefer Newsgroups: gmane.emacs.devel Subject: Re: A unified project root interface Date: Tue, 19 Mar 2013 08:33:22 +0100 Message-ID: <20130319083322.08bfd192@forcix.kollektiv-hamburg.de> References: <20130309174419.6e1cadb4@forcix.kollektiv-hamburg.de> <87hakh2299.fsf@fimbulvetr.bsc.es> <513FBA1C.5040100@siege-engine.com> <87vc8vyy66.fsf@engster.org> <5143C11D.8070705@siege-engine.com> <87sj3vv35h.fsf@engster.org> <20130316160203.6b889aba@forcix.kollektiv-hamburg.de> <87ehffuf1g.fsf@engster.org> <20130317001630.125e1987@forcix.kollektiv-hamburg.de> <87y5dmsz5u.fsf@engster.org> <20130317191817.764a44f5@forcix.kollektiv-hamburg.de> <87ppywtj9s.fsf@engster.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1363678413 32084 80.91.229.3 (19 Mar 2013 07:33:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 19 Mar 2013 07:33:33 +0000 (UTC) Cc: emacs-devel@gnu.org To: David Engster Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Mar 19 08:33:58 2013 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 1UHr3W-0008EB-HL for ged-emacs-devel@m.gmane.org; Tue, 19 Mar 2013 08:33:58 +0100 Original-Received: from localhost ([::1]:38405 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UHr39-0006Pz-Dp for ged-emacs-devel@m.gmane.org; Tue, 19 Mar 2013 03:33:35 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:58541) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UHr35-0006Pn-KX for emacs-devel@gnu.org; Tue, 19 Mar 2013 03:33:33 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UHr30-00021N-Pf for emacs-devel@gnu.org; Tue, 19 Mar 2013 03:33:31 -0400 Original-Received: from istinn.electusmatari.com ([83.169.37.145]:55692) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UHr30-00021F-Gx for emacs-devel@gnu.org; Tue, 19 Mar 2013 03:33:26 -0400 Original-Received: from forcix.kollektiv-hamburg.de (hmbg-5f7626f7.pool.mediaWays.net [95.118.38.247]) by istinn.electusmatari.com (Postfix) with ESMTPSA id 49423D10001E; Tue, 19 Mar 2013 08:33:24 +0100 (CET) In-Reply-To: <87ppywtj9s.fsf@engster.org> X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.10; i486-pc-linux-gnu) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 83.169.37.145 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:157948 Archived-At: On Mon, 18 Mar 2013 23:50:23 +0100 David Engster wrote: > Yes, functions like `ede-project-root-directory' are actually methods, > but why does it matter? Nothing. I don't have a problem with CLOS (I think you might be confusing me with another person who mentioned a distaste for CLOS). A method for me has a complexity of a function with one required argument. Which is, a higher complexity than a function with no arguments. ;-) > I'm willing to code the necessary stuff on the EDE side of things; if > it turns out too complicated to use for package maintainers, I have no > problem throwing it away. This is the tricky part. I do not know what is "too complex", and it's difficult to predict this. The only way is to try and provide a very simple API and see if it gets adopted. As to EDE/CEDET's complexity, I hope that "oh no, the memory usage" or "oh no, the load time" isn't a *huge* concern if the API is simple enough. It would be great if EDE has such a simple entry point to allow for expansion and better integration between packages. That is, you can use this API without knowing anything else, and when you need more, you can stumble into the CEDET manual and go "woah, it's full of stars". ;-) My original idea was to provide an API that CEDET/EDE can build upon, too, but I don't really care either way. > This can be done. I will need a bit of time though, since I really > need to do another CEDET merge round with current trunk first. I > think I'll be able to come up with something in the coming weeks. Thank you for your willingness to support this! > > - Ask authors of extensions to use (ede-minor-mode 1) in their mode > > function and simply use that function in their modes. > > Not sure if it's a good idea to enable EDE behind the user's back; I > think they should enable it in their init file if they want to have > project support. But IMO that's a detail; let's cross that bridge when > we get there. Yes, it's a detail. I'm trying to replicate the current use case in e.g. find-file-in-project where the user simply has to install ffip as a package and can use the function without having to configure anything else. Regards, -- Jorgen