At 10:19 AM 4/20/00 -0400, you wrote:
>
>>4. Can the debugger reuse the CLI, Local Variables, Threads, and debug
>>Process buffers? They tend to build up over time.
>>
>
>Yes. I could make this an option I suppose.
>I have the following bound to f12
>
>(defun myjde-bug-kill-debugger()
>"Exit the debugger and kill all dead process buffers."
> (interactive)
> (progn
> (jde-bug-exit)
> (jde-bug-remove-dead-processes)
> (delete-other-windows)))
>
>>>6. I get a java window when running JDEbug, and I think it's from the
>>>debugger, not the debuggee as it is still present after the debuggee
>>>terminates. Could this use javaw or, alternately, minimize the window?
>>>
>>
>>Set jde-run-java-vm-w to javaw. This is the default by the way. You must
>>have changed it when you were using NT/XEmacs.
>
>I would actually preferr to let this window run if the CLI output would go
>there instead. I don't know if this is an option or not.
>
No. Why would you prefer this anyway?
The JDE creates a CLI buffer for each process where you can view the
debugee process's output. If what you're after is the output displayed in a
separate frame, simple select the CLI buffer and execute C-x 5 2.
My plan is to make all of this configurable in an upcoming release.
- Paul
------------------------------------------------------------
TECH SUPPORT POLICY
I respond only to requests that contain a complete problem report. The
easiest way to ensure that your report is complete is to include the output
of the JDE->Help->Submit Problem Report command in your request.
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
