At 12:42 PM 3/29/00 +0200, you wrote:
>
>> Thank you. This kind of detailed feedback is very useful. I
>> will try to correct the problems you have noted.
>>
>:)
>
>I have some more bugs for you. ;)
>
>* If I debug Foo.java (i.e. the '=>' symbol is currently in Foo.java) and you
>switch to some other buffer containing Java code and then try to single step,
>then JDEbug does not like that situation very much at all.
>
>I suggest that I should be transfered back to the correct buffer (i.e.
>pop-to-buffer or something) and to the correct position in the buffer (i.e. to
>the line where the '=>' symbol is).
>
Yes.
>If I have several debugging sessions running at the same time, it would be
nice
>to get a pop up window (or something) listing the buffers where debugging
>sessions are currently running. Selecting one of the buffers should then
>transfer me to that buffer etc.
>
>Another approach would be to just make the correct buffer visible and not move
>the focus from the current buffer.
>
I'm not sure what you mean. The JDEBug allows you to run only one debug
session at a time in the current Emacs session. However, you can launch and
debug multiple processes in a single session, each with its own window
configuration. Each process is given an ID number. At any given moment,
JDEbug commands apply to only one of these processes, known as the target
process. You can use the Set Target Process to switch processes. When you
switch to a process, the JDE redisplays the targets window configuration.
Currently the Set Target command prompts you to enter the target ID. My
plan is to add a command that would display a popup buffer listing the
currently active processes, with the current target process highlighted.
You could then switch to any other process by clicking its entry in the
active process list buffer.
>
>* Set a breakpoint. Copy some code. Place point on the breakpoint and paste it
>in. The new text will be colored as the breakpoint. If the breakpoint is
>cleared
>all the coloring is removed.
>
Yes. This is part of the general problem that the JDE does not try to
update breakpoint locations to reflect changes to the source code.
>
>This one is more like a feature request. I think that if any of the JDEbug
>buffers are selected, the JDEbug menu should not disappear (or atleast the
>keybindings should not disappear).
>
>This happens frequently when you use the tree list in the local variables
>buffers.
>
>Perhaps you should not transfer focus if you are located in any of the JDebug
>buffers? The assumption would then be that you want to stay in the buffer (for
>instance the local variables buffer) and continue to do things.
>
Yes. This would be good, especially if the JDE greyed out commands that did
not apply to the current buffer, e.g., Set Breakpoint.
- Paul
------------------------------------------------------------
ASKING FOR TECHNICAL SUPPORT ON THE JDE LIST
Please use the JDE->Help->Submit Problem Report command when reporting a
bug or seeking help. This command generates a complete snapshot of your
system. Submitting such a snapshot increases the chances that your request
will get a swift response.
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
