Does anybody know how to configure JDEbug so that when
starting a debugging session, it shows precisely these
three buffers :
- source code (with breakpoints)
- local variables
- CLI (command-line interface)
Maybe through adding a hook, maybe using customization
options jde-db-mode-hook or
I often get lisp problems with JDEBug (on
Xemacs/solaris). Error message is (void-variable
old-assoc).
Any hint on that ?
Sometimes, the message buffer shows me something
like:
Error: evaluating output from the debugger caused a
Lisp error.
Debugger output: (jde-dbo-event-set 3 none nil
Hello,
When using jde-show-class-source and picking through a list of possible
classes
to open, the OK button provides the error whose trace is reproduced below. I
can provide the JDE problem report file is this can help.
Has anoybody ever experienced the problem (I'm using ecb 1.80, but even
old-assoc is actually a function in XEmacs. I don't know why you would be
seeing this. Did you update eieio and semantic as well as jde?
andy
-Original Message-
From: fred bapst [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 30, 2002 1:37 AM
To: [EMAIL PROTECTED]
Subject:
I've been using JDE for a while, and while I'm generally happy with it,
there is some basic functionality that it seems to be missing:
* Minibuffer completion on class names for jde-open-class-source.
* Find usages functionality: list all callers/users for a given
method, field or class.
Galen Boyer writes:
Hi Paul,
I know you recommend eieio highly. Do you have a simple explanation of
how you use it, along the lines of your simple/elegant description of
how you connected Elisp to a JVM? (Feel free to forward this to the JDE
list if you feel it is appropriate for
