[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Emacs learning curve
From: |
Lennart Borgman |
Subject: |
Re: Emacs learning curve |
Date: |
Mon, 2 Aug 2010 20:43:53 +0200 |
On Mon, Aug 2, 2010 at 8:39 PM, Tom <address@hidden> wrote:
>
> And why not add these by simply reusing the work of others?
>
> The most requested and popular features are code
> completion, refactoring and such. I know CEDET can do some of
> these, but I wonder if Emacs should harness the effort put into
> these areas by other development teams.
>
> Take a look at the screenshots IdeBridge for example:
>
> http://www.emacswiki.org/emacs/IdeBridge
>
>
> It uses SharpDevelop libraries to provide completion. I know a
> pure elisp solution would be the best, but given the plethora of
> languages it's not a realistic goal to provide a comprehensive
> Elisp backend solution for everything due to limited developer
> resources.
>
> The best approach may be to provide a standard code
> completion (refactoring, documentation lookup, etc.) frontend in
> Emacs into which any backend implementation can be
> plugged. People would write bridge code like in the above example
> to handle communication between the frontend and the selected
> backend. There are no licensing issues, because it can work
> with process communication.
I think that CEDET already makes this possible, but Eric can surely
give a better answer. (Maybe this should be pointed out very clearly
in Emacs doc, at least as a goal?)
Re: Emacs learning curve, Stephen J. Turnbull, 2010/08/02
Re: Emacs learning curve, Andy Wingo, 2010/08/03
Re: Emacs learning curve, Ted Zlatanov, 2010/08/02
RE: Emacs learning curve, grischka, 2010/08/02