unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Alan Shutko <ats@springies.com>
To: emacs-devel@gnu.org
Subject: Re: Implementing Eclipse's "organize-imports" in Emacs Lisp
Date: Fri, 25 Jan 2008 10:40:13 -0600	[thread overview]
Message-ID: <87odb9dfki.fsf@vera.springies.com> (raw)
In-Reply-To: <87prvqwbc1.fsf@member.fsf.org> (Tassilo Horn's message of "Fri,  25 Jan 2008 09:36:46 +0100")

Tassilo Horn <tassilo@member.fsf.org> writes:

> Anyway, it's exciting to see that it's feasible to control eclipse from
> an external app.

I've semi-adopted RemoteEclipse[1], which consists of an Eclipse plugin and
some elisp that uses beanshell and java rpc to communicate to Eclipse.
It was limited to pulling the project information (classpath,
directories, etc) from Eclipse, triggering builds, and retrieving error
information into a *compile* buffer.  It didn't attempt to integrate
with Eclipse's project navigation or rafactoring features, instead
allowing JDEE tools to handle it. 

I've somewhat updated it to work with Eclipse 3.x[2] but Eclipse 3
changed to do compilation in a background thread, and that would really
require a fair rework of the whole plugin.  I'd also like to change the
communication path... beanshell to java rpc just bugs me.

I think there are some good ideas in RemoteEclipse, but it might be
easier to start with fresh code.

Footnotes: 
[1]  Formerly at
http://www.raffael.ch/index.jsp?content=page/FTP/RemoteEclipse, but the
site appears to be down.

[2]  http://www.springies.com/~ats/RemoteEclipse.zip

-- 
Alan Shutko <ats@acm.org> - I am the rocks.
I worship the ground that awaits you.

  reply	other threads:[~2008-01-25 16:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-22 10:53 Implementing Eclipse's "organize-imports" in Emacs Lisp Paul Michael Reilly
2008-01-22 14:09 ` Lennart Borgman (gmail)
2008-01-24  8:07   ` Paul Michael Reilly
2008-01-24  8:17     ` Lennart Borgman (gmail)
     [not found]     ` <4798473D.1010505-9u8/wbatHBfQT0dZR+AlfA@public.gmane.org>
2008-01-24 13:59       ` Carlos Konstanski
2008-01-24 18:41         ` [jdee-users] " Paul Michael Reilly
2008-01-25  0:53       ` Yee Keat Phuah
2008-01-25  0:26         ` Tom Tromey
2008-01-25  8:36           ` Tassilo Horn
2008-01-25 16:40             ` Alan Shutko [this message]
2008-01-22 15:54 ` Tom Tromey
2008-01-28  7:18 ` Richard Stallman
2008-01-28  8:05   ` Miles Bader
2008-01-28 21:33     ` Richard Stallman
2008-01-28 12:09   ` Paul Michael Reilly
2008-01-28 21:32     ` Richard Stallman
  -- strict thread matches above, loose matches on Subject: below --
2008-02-07 19:05 Klotz, Leigh

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=87odb9dfki.fsf@vera.springies.com \
    --to=ats@springies.com \
    --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).