unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Tassilo Horn <tassilo@member.fsf.org>
To: Lennart Borgman <lennart.borgman@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Is JDEE moribund? Is Emacs a viable Java devel environment?
Date: Sat, 18 Apr 2009 00:52:16 +0200	[thread overview]
Message-ID: <87ws9i6ggv.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <e01d8a50904171508re2bb804y1c6242bd61970762@mail.gmail.com> (Lennart Borgman's message of "Sat, 18 Apr 2009 00:08:12 +0200")

Lennart Borgman <lennart.borgman@gmail.com> writes:

Hi Lennart,

>> I hope someone starts writing an emacs interface to Eclim [1] anytime
>> soon.  I had a quick look at the sources and it shouldn't be too
>> hard, but it's quite a lot to do (to get all eclipse features).
>>
>> To me it seems that most java programmers use eclipse (or netbeans)
>> anyway or switched to eclipse/NB, and there's noone feels preasured
>> to enhance emacs in that direction.  And you can count me as one of
>> those, sadly.  But I'm pretty sure that if someone would create an
>> emacs interface to let's say only the autocompletion feature of
>> eclipse using eclim, things would get running on their own.
>
> There has been very much done to CEDET now. Would it not be a good
> idea to use CEDET for an interface to eclim?

CEDET uses another approach.  It has it's own parsers and analyzers
which enable it to do smart autocompletion and other intelligent stuff.
This works quite well for C/C++, because Eric has put a lot of effort
into it, and I highly appreciate that.

The eclim approach is very different.  Here an headless eclipse instance
runs as a server in the background.  Vim does no intelligent source code
analysis, instead it sends only a plain text command to eclipse like:

   I'm in project Foo in file src/bar/Baz.java on position 18271 and now
   I executed the completion command.  Gimme the completion list,
   please.

And so does eclipse.  Here the editors task is only to issue commands,
let eclipse do the intelligent stuff, get back the results, and display
it.  Very simple.

IMO this is a great approach, because speaking honestly: Emacs cannot
compete with eclipse for java (and probably other new, nifty languages
like scala or groovy).  They have far more developers and academia as
well as industry are focused on it.

Anyway, no reason for sadness, the functionality is there ready for
consumption.  So instead of reinventing the wheel, we should combine
emacs' unsurpassed editing capabilities (eclipse extremely sucks in that
respect) with eclipse's intelligent features where those are better than
the emacs counterparts.

Bye,
Tassilo




  reply	other threads:[~2009-04-17 22:52 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17  6:03 Is JDEE moribund? Is Emacs a viable Java devel environment? eefacm
2009-04-17 13:15 ` Martin
2009-04-17 17:19   ` eefacm
2009-04-18  1:15     ` Tim X
2009-04-17 17:28   ` Richard Riley
2009-04-17 19:50     ` Tassilo Horn
2009-04-17 22:08       ` Lennart Borgman
2009-04-17 22:52         ` Tassilo Horn [this message]
2009-04-17 23:32           ` Lennart Borgman
2009-04-18  8:05             ` David Engster
2009-04-18 11:32             ` An Eclim frontend for Emacs (was: Is JDEE moribund? Is Emacs a viable Java devel environment?) Tassilo Horn
2009-04-18 12:33               ` Lennart Borgman
2009-04-18 14:30                 ` Re[1]: " Eric M. Ludlam
2009-04-18 18:40                   ` An Eclim frontend for Emacs Tassilo Horn
2009-04-18 21:00                     ` Nikolaj Schumacher
2009-04-18 22:06                       ` Tassilo Horn
2009-04-19 12:18                         ` Nikolaj Schumacher
2009-04-19 16:59                           ` Tassilo Horn
2009-04-20  6:58                             ` Nikolaj Schumacher
2009-04-20  7:12                               ` Tassilo Horn
2009-04-20 18:56                           ` Tassilo Horn
2009-04-22  6:04                             ` Nikolaj Schumacher
2009-04-22  6:54                               ` Tassilo Horn
2009-04-22 18:08                                 ` Nikolaj Schumacher
2009-04-22 18:32                                   ` Tassilo Horn
     [not found]                           ` <mailman.5741.1240253822.31690.help-gnu-emacs@gnu.org>
2009-04-20 20:00                             ` Richard Riley
2009-04-21 17:24                               ` Tassilo Horn
     [not found]                               ` <mailman.5771.1240334666.31690.help-gnu-emacs@gnu.org>
2009-04-28 20:33                                 ` Chris McMahan
2009-04-29 23:40                                   ` Tassilo Horn
     [not found]                                   ` <mailman.6285.1241048434.31690.help-gnu-emacs@gnu.org>
2009-05-01  2:58                                     ` Chris McMahan
     [not found]                       ` <mailman.5655.1240092382.31690.help-gnu-emacs@gnu.org>
2009-04-18 22:13                         ` Richard Riley
2009-04-18 22:44                       ` Re[2]: " Eric M. Ludlam
     [not found]         ` <mailman.5568.1240008748.31690.help-gnu-emacs@gnu.org>
2009-04-18 14:25           ` Is JDEE moribund? Is Emacs a viable Java devel environment? Richard Riley
     [not found]       ` <mailman.5561.1240006100.31690.help-gnu-emacs@gnu.org>
2009-04-18 14:23         ` Richard Riley
2009-04-17 18:01 ` hazlup

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=87ws9i6ggv.fsf@thinkpad.tsdh.de \
    --to=tassilo@member.fsf.org \
    --cc=help-gnu-emacs@gnu.org \
    --cc=lennart.borgman@gmail.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.
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).