unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Colascione <dancol@dancol.org>
Cc: emacs-devel@gnu.org
Subject: Re: Project systems (again)
Date: Fri, 18 Apr 2014 09:37:00 +0300	[thread overview]
Message-ID: <83y4z3gn3n.fsf@gnu.org> (raw)
In-Reply-To: <53504D2C.7070504@dancol.org>

> Date: Thu, 17 Apr 2014 14:52:44 -0700
> From: Daniel Colascione <dancol@dancol.org>
> 
> I'd like to include a good, minimal "project system" in Emacs 24.5 and
> turn it on by default.

IMO, this would be a very good progress, thanks.

> EDE already provides some of the functionality I've described above, but
> I don't like the way it does it. It's very complicated and embeds
> uncommon features into the core. EDE's reliance on EIEIO and its large
> feature-set create difficulties dumping the system with Emacs. And have
> you tried actually creating a new EDE project type? It's surprisingly
> and disappointingly difficult. Ad-hoc extensibility with EDE is hard
> because of its EIEIO use, and I don't think EIEIO is buying us anything,
> really.
> 
> EDE also includes many features that are not generally useful (like
> makefile generation) and that complicate the codebase. EDE being
> developed out-of-tree makes it hard to fix these issues. I'd rather have
> a minimal and more idiomatically Emacs-ish core facility that EDE can
> build on. EDE is also not currently integrated with VC, and it doesn't
> provide nice user interfaces (ede-find-file, for example, doesn't do
> completion.)

FWIW, I'd prefer that you work with EDE developers to improve and
extend what they have; starting from scratch (or almost from scratch)
sounds like waste of effort, especially since some of the EDE is
already in Emacs.  I find the Makefile generation feature useful
(e.g., when you need to develop on one platform, then build the same
code and run it on another, where the full development environment is
not necessarily installed).  In any case, I don't see how unused
features could get in your way too much, unless their design is wrong.



  reply	other threads:[~2014-04-18  6:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-17 21:52 Project systems (again) Daniel Colascione
2014-04-18  6:37 ` Eli Zaretskii [this message]
2014-04-18  7:07   ` Daniel Colascione
2014-04-18  7:50     ` Eli Zaretskii
2014-04-18  7:58       ` Daniel Colascione
2014-04-18  8:49         ` Eli Zaretskii
2014-04-19  1:45         ` Eric M. Ludlam
2014-04-19 14:26           ` Stefan Monnier
2014-04-19 19:37             ` Eric M. Ludlam
2014-04-18 15:52     ` Stefan Monnier
2014-04-18 18:37     ` Alex Ott
2014-04-18 14:03   ` Dmitry Gutov
2014-04-19  8:55     ` Bozhidar Batsov
2014-04-19 14:28       ` Stefan Monnier
2014-04-19 16:52       ` Daniel Colascione

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=83y4z3gn3n.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dancol@dancol.org \
    --cc=emacs-devel@gnu.org \
    /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).