Would your patch to "etags.el" work with the one released in GNU Emacs?
I've always been annoyed with this problem, and it would be useful to get it
fixed at the "highest level", as opposed to just releasing it with the JDE.
> ----------
> From: Jim Holmlund[SMTP:[EMAIL PROTECTED]]
> Sent: Friday, March 17, 2000 11:52 AM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: Re: Is there a command line interface for JDEbug?
>
> Paul Kinnucan writes:
> > At 02:50 PM 3/13/00 -0800, you wrote:
> :
> :
> < no cmd line mode for JEDbug>
>
>
> Paul, thanks for the info on JDEbug. BTW, in case you are interested,
> I have a modified version of etags.el that fixes some bugs that
> are in the etags.el in xemacs21.1 patch 3 (such as searching for
> 'String' will find 'public String gus()' instead of the defn of String.
> If you are interested, let me know and I will send it to you.
>
> (Also, you are probably not interested in this because it is not java,
> but when sun released the non-tooltalk version of dbx a few years
> ago, we lost the ability to run dbx under gud.el. I have a modified
> version of gud.el that fixes this. It puts up a debugging toolbar
> containing the usual buttons and allows you to run dbx in a comint
> buffer just like you can gdb. If you are interested in this, let me
> know.)
>
>
>
>
> > >If I run with the old jdb stuff in JDE, I get a comint buffer that
> > >behaves much like a normal
> > >gud.el buffer.
> > >
> > >But, when I use the new JPDA stuff, I don't see that I have such a
> > >buffer
> > >The only comint buffer I see is one named *JDEbug* which contains
> stuff
> > >like
> > >
> > >
> > > (jde-dbo-init-debug-session)
> > > JDE> -1 17 launch 3 -vmexec java FileTest
> > >
> > >
> > >
> > > (jde-dbo-message
> > > 3 "Launched VM Java Debug Interface (Reference Implementation)
> > > version 1.0
> > > Java Debug Wire Protocol (Reference Implementation) version
> > > 1.0
> > > JVM Debug Interface version 1.0
> > > JVM version 1.2.2 (Classic VM, build JDK-1.2.2-001, green
> > > threads, nojit)")
> > >
> > >
> > > (jde-dbo-command-result 17 63803)
> > >
> > > JDE> 3 18 break absolute FileTest.java 9
> > >
> > >It looks like the "JDE>" is a prompt, and the stuff following is a
> > >command, followed by
> > >lines that contain the output of the command.
> > >
> > >Is this buffer just intended for internal use?
> >
> > Yes. Unlike dbx, gdb, jdb, JDEbug is not a command-line debugger. It
> was
> > designed from the beginning as an extension of Emacs. Unfortunately,
> the
> > only mechanism that Emacs provides for extensions that require non-Lisp
> > code is to implement the non-Lisp portion as an external executable
> linked
> > to Emacs via a socket or standard I/O. That limitation dictated the
> design
> > of JDEbug, it consists of an Emacs Lisp frontend and a Java backend
> that
> > communicate via standard I/O. The frontend drives the backend by
> issuing
> > commands. The backend's responses are in the form of Lisp forms to
> avoid
> > the need for a parser on the Lisp side. The *JDEbug* buffer provides a
> > transcript of this low-level interaction for development and debugging
> > purposes.
> >
> > >If so, are there any
> > >plans for a cmd line interface ala
> > >dbx, gdb, jdb, ....?
> > >
> >
> > No.
> >
> > >If not, is there a doc somewhere explaining
> > >the command language (eg, -1 17 launch 3 -vmexec java FileTest)?
> > >
> >
> > The command syntax is documented in the Java source code that is
> > distributed with the JDE.
> >
> > - Paul
> >
> >
> --------------------------------------------------------------------------
> ----
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> > JDE website: http:/sunsite.auc.dk/jde/
> >
> > JDE mailing list archive:
> > http://www.mail-archive.com/[email protected]/maillist.html
> >
> > Please use JDE->Help->Submit Problem Report when reporting a bug or
> seeking
> > help. This will insure that you include all information that may be
> > required to solve your problem.
> >
>
