Paul == Paul Kinnucan [EMAIL PROTECTED] writes:
Paul It also allows users who are, like myself, working in a
Paul multilanguage environment (e.g., C/C++/Java) to use a single
Paul environment for all their work.
This is my primary motivation for using emacs, and JDE for java. I use
many
ECB 1.92 is released!
=
Reminder:
The homepage of ECB has moved to http://ecb.sourceforge.net
http://ecb.sourceforge.net . The old
homepage at http://home.swipnet.se/mayhem/ecb.html
http://home.swipnet.se/mayhem/ecb.html is not longer supported.
How to get it:
Hi,
When I use 'jde-import-find-and-import' in ECB with a compile window, the
prompt window that asks for clarification pops up in the compilation buffer.
This is fine. But then, it doesn't have an idea where to put the import
statement. Is there a setting in JDE/ECB that I can tweak to
Ralph Jorre writes:
I don't often use a debugger but I have found JSwat very good and I just
wonder if it wouldn't be more efficient to just include some hooks so as
to be able to incorporate it efficiently.
Maybe this would be easier to maintain than rewriting the debug.
I plan
Klaus,
Thanks for your enhancements. I am a beginner lisp programmer
(which may have been revealed by my long winded coding style and indentation
and incomplete knowledge of what is already available in base emacs
packages).
Where I want to take this idea is to:
1. Run a background compilation
I had thought of this as well. Perhaps the JSwat maintainer would be
interested in working on it. If you download the JSwat CVS code, you
see they arleady use JDEE. See:
http://home.nc.rr.com/nascifandelaine/jswat.el
Paul Kinnucan [EMAIL PROTECTED] writes:
Ralph Jorre writes:
I don't
On Fri, 21 Feb 2003, [EMAIL PROTECTED] wrote:
It is hopeless for the JDEE to try to compete
feature-for-feature with dedicated Java IDE's, especially
commercial IDE's.
Maybe to further this, create an email list called, jde-plugin,
or something like it. Then, as people want to discuss this
Hi all,
I have some questions about managing imports in JDEE.
1. I see that there is a very nice `jde-import-organize' and
`jde-import-collapse-imports' functions. But what if I want to expand an
import of java.util.* to only classes that I'm using?
2. In WSAD, when I organize imports, it
Le Wang writes:
Hi all,
I have some questions about managing imports in JDEE.
1. I see that there is a very nice `jde-import-organize' and
`jde-import-collapse-imports' functions. But what if I want to expand an
import of java.util.* to only classes that I'm using?
2. In
-Original Message-
From: Paul Kinnucan [mailto:[EMAIL PROTECTED]
Sent: Monday, February 24, 2003 12:15 PM
To: Le Wang
Cc: [EMAIL PROTECTED]
Subject: managing imports
--8-snip8-
People have suggested adding a command to import all
--- Chitale, Sandip V [EMAIL PROTECTED] wrote:
No. I had written a BCEL based tool to parse a class file
and dump the imports. Nick Sieger had wrapped it in some
lisp code also.
That's pretty ingenious. But does anyone think this should be possible
without parsing a compiled class file?
Galen Boyer writes:
On Fri, 21 Feb 2003, [EMAIL PROTECTED] wrote:
It is hopeless for the JDEE to try to compete
feature-for-feature with dedicated Java IDE's, especially
commercial IDE's.
Maybe to further this, create an email list called, jde-plugin,
or something like it.
Chitale, Sandip V [EMAIL PROTECTED] seems to think that:
[ ... ]
2. Indicate the error messages using an underline (or user customizable) face
(say!) over the extent of the buffer text causing the error.
(unfortunately not all compilers give the column or column range where
the error is).
3.
13 matches
Mail list logo