At 11:02 AM 10/7/99 -0700, Jeff Finger wrote:
>Environment:
> "Operating" System: WinNT 4.0 SP 5
> Emacs: 20.4.1
> JDE: jde-2.1.6beta10
> JDK: JDK 1.2.1
>
>I set a breakpoint in main, run jde-debug, and hit the breakpoint. At
>that time, my model of things is that the *JDEbug* buffer should have
>a "JDE> " prompt to which I can type JDE commands, but that is not what
>happens. Instead, there is no prompt and there does not seem to be
>a response when I type commands in *JDEbug*. Is my model wrong or is
>something going wrong?
>
Not entirely. The primary "user" of JDEBug's command line interface is
intended to be Emacs itself. That is why JDEBug responds to commands in
Lisp. The intention is that other users, namely us humans, will interact
with JDEBug via Emacs menus, M-x commands, and keyboard shortcuts. The
*JDEBug* buffer is intended primarily for debugging and development
purposes. That is why the JDE buries it when it starts JDEBug for you. The
*JDEbug* buffer allows me, the developer, to enter JDEBug CLI commands and
see the raw output of JDEBug unfiltered by Emacs (or more precisly the JDE
Lisp code). I put a prompt into the *JDEbug* buffer primarily to assist me
to enter commands. I didn't intend it for general use. If you want to enter
raw commands and interpret the Lisp output, go ahead. You can enter
commands after any debugger output, whether a prompt is there or not.
Perhaps someday somebody will write a higher-level, more human friendly CLI
interface on top of JDEbug's basic CLI. This of cource could be done
entirely in elisp.
- Paul
