From: David Engster <deng@randomsample.de>
To: "Eric M. Ludlam" <eric@siege-engine.com>
Cc: emacs-devel@gnu.org
Subject: Re: A unified project root interface
Date: Sat, 16 Mar 2013 15:18:50 +0100 [thread overview]
Message-ID: <87sj3vv35h.fsf@engster.org> (raw)
In-Reply-To: <5143C11D.8070705@siege-engine.com> (Eric M. Ludlam's message of "Fri, 15 Mar 2013 20:47:25 -0400")
Eric M. Ludlam writes:
> On 03/13/2013 02:03 PM, David Engster wrote:
>> There's no doubt that EDE can do all what's needed, but is has to be
>> wrapped in something that's easier to use, at least for simple stuff
>> like what project-roots.el does.
>
> Ok, I can buy that. EDE was never simple. I just know that if an
> "official" project mechanism is built, I'll have some work to do. ;)
I think we don't need another project mechanism in Emacs. EDE and
dir-locals should be enough. What we have to do however is to develop at
least one very basic project type in EDE which can be used similar to
project-root.el. I think what Sudish Joseph explained in this thread is
pretty typical:
- Recognizing projects based on some files or directories which are in
the current directory or further up the tree.
- The ability to ask Emacs of what project the current buffer is part
of.
- Automatic setting of variables based on the current project.
The user should be able to configure this in a variable, similar to how
project-root.el does it. For example:
("Perl Project"
:root-contains ("t" "lib")
:on-load 'some-function
:variable-settings '((tab-width . 4)
(fill-column . 79)))
This is easy to implement with EDE. I can work on this, but I'd like to
finish my five other things which are 90% finished first...
> Also be aware that I ran into a lot of performance issues I had to
> work through with EDE project detection. Once other code starts
> asking where it is in a project, it's amazing how often that stuff
> gets called. A project cache is a super handy thing, and was one of
> the key performance improvements I made back when i was trying to
> speed up smart completion.
Yes, I know. This is why I think EDE should be the framework on which
those things are built.
-David
next prev parent reply other threads:[~2013-03-16 14:18 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-09 16:44 A unified project root interface Jorgen Schaefer
2013-03-09 17:12 ` Fabian Ezequiel Gallina
2013-03-10 5:38 ` Stefan Monnier
2013-03-10 10:06 ` Jorgen Schaefer
2013-03-11 18:57 ` Lluís
2013-03-12 23:28 ` Eric M. Ludlam
2013-03-12 23:42 ` Jorgen Schaefer
2013-03-13 2:02 ` Eric M. Ludlam
2013-03-13 18:03 ` David Engster
2013-03-13 19:11 ` Sudish Joseph
2013-03-16 0:47 ` Eric M. Ludlam
2013-03-16 14:18 ` David Engster [this message]
2013-03-16 15:02 ` Jorgen Schaefer
2013-03-16 22:27 ` Phil Hagelberg
2013-03-16 22:59 ` David Engster
2013-03-16 23:16 ` Jorgen Schaefer
2013-03-17 17:40 ` David Engster
2013-03-17 18:18 ` Jorgen Schaefer
2013-03-18 22:50 ` David Engster
2013-03-19 1:57 ` John Yates
2013-03-19 7:18 ` David Engster
2013-03-19 12:23 ` Eric M. Ludlam
2013-03-19 13:06 ` Stefan Monnier
2013-03-19 19:09 ` David Engster
2013-03-20 3:21 ` Stefan Monnier
2013-03-20 4:48 ` Leo Liu
2013-03-20 7:04 ` joakim
2013-03-20 7:05 ` David Engster
2013-03-20 7:13 ` David Engster
2013-03-20 12:57 ` Stefan Monnier
2013-03-20 16:14 ` Davis Herring
2013-03-20 17:41 ` Stefan Monnier
2013-03-20 17:48 ` Stefan Monnier
2013-03-20 18:20 ` Bruce Korb
2013-03-20 22:14 ` Stefan Monnier
2013-03-20 16:34 ` David Engster
2013-03-20 17:47 ` Stefan Monnier
2013-03-21 0:55 ` Eric M. Ludlam
2013-03-21 3:27 ` Stefan Monnier
2013-03-21 4:07 ` Eric M. Ludlam
2013-03-21 14:33 ` Stefan Monnier
2013-03-22 2:12 ` Eric M. Ludlam
2013-03-23 11:04 ` EIEIO split (was: A unified project root interface) David Engster
2013-03-21 16:32 ` A unified project root interface David Engster
2013-03-22 0:47 ` Eric M. Ludlam
2013-03-22 20:30 ` David Engster
2013-03-23 17:10 ` Eric M. Ludlam
2013-03-23 17:26 ` Jorgen Schaefer
2013-03-23 18:02 ` Dmitry Gutov
2013-03-23 20:51 ` Pascal J. Bourguignon
2013-03-24 4:25 ` Dmitry Gutov
2013-03-24 10:13 ` Jorgen Schaefer
2013-04-06 13:25 ` Jorgen Schaefer
2013-04-06 17:13 ` Eric M. Ludlam
2013-04-08 19:03 ` David Engster
2013-12-31 20:12 ` Daniel Colascione
2013-03-20 17:49 ` Jorgen Schaefer
2013-03-19 7:33 ` Jorgen Schaefer
2013-03-17 8:08 ` joakim
2013-03-12 15:34 ` Sudish Joseph
2013-03-12 16:51 ` Dmitry Gutov
2013-03-12 18:23 ` Ted Zlatanov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sj3vv35h.fsf@engster.org \
--to=deng@randomsample.de \
--cc=emacs-devel@gnu.org \
--cc=eric@siege-engine.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).