At 11:54 AM 8/14/99 -0700, you wrote:
>Thanks for the work on improving the debugger interface.
>However, I would like to request that you NOT remove a command
>line interface. Debugging can be a very input-oriented
>and detailed exercise. In many situations, it can be (at least
>for those who type well), much faster to type a command
>(especially if aliases and macros are allowed) than "point-and-click".
>Both interfaces are valuable: why exclude one and its benefits?
>Your planned use of Lisp and Java statements make a command
>line interface even more compelling. If you think it is
>too complex or intimidating for the beginner, make it
>optional.
>
There will be a command line interface, but it will not be
very friendly. Currently the new debugger is set up so that
when you start the debugger, the JDE creates
and promptly buries a comint buffer that records commands
that it sends to the debugger and the debugger's
responses. The user is free to display the buffer and enter
commands. But note that each command must include a unique
command id and the id of the process at which the command
is targeted. Also the debugger's responses are in the
form of Lisp code.
Also, please recognize that selecting items from a menu and
entering commands in the comint buffer are not the only way
to control the debugger. There are two other alternatives:
keystroke shortcuts and executing Emacs commands, e.g., you
can set a breakpoint at the current line in the
current buffer in the following ways:
1. Select Set Breakpoint from the JDEbug menu.
2. Enter a keystroke combination of your own or the JDE's choosing.
3. Type M-x jde-bug-set-breakpoint in the minibuffer.
4. Type the following in the comint buffer:
1 55 break absolute Foobar.java 100
I have a fair amount of experience with Microsoft's Visual C++
debugger. It has no command line facility yet manages to be quite
powerful and flexible nonetheless.
Please not also that the JDE will continue to support JDB so it is
an alternative for those who prefer a command-line interface.
While I'm on the subject, I'd like to get your opinion on
how to manage multiple processes. My current plan is for the JDE debugger
to implement the notion of a target process. Most JDE commands will
apply to the target process, e.g., step commands. The user selects which of
the processes
being debugged is the target process at any given time. The advantage
of this approach is it avoids the user having to specify which process
a command applies to when multiple processes are being debugged. The user
simply selects a target process and as long as that process is selected,
all commands apply to it.
How does this strike you?
- Paul
