Re: [ jEdit-devel ] Debugging plugins

[Rick G. <ric...@ea...>]

So you have to go through a complete build each time and make a new jar
before testing?  Do plugins have to be loaded via the jars directory? Are
there any alternatives?

Thanks for the advice.

-rick

----- Original Message -----
From: "mike dillon" <md...@st...>
To: <jed...@li...>
Sent: Sunday, February 06, 2000 5:54 PM
Subject: Re: [ jEdit-devel ] Debugging plugins


> On Sun, 6 Feb 2000, Rick Gibbs wrote:
> > I was wondering if anybody had any advice for debugging plugins?  How
are
> > people developing the plugins that are out there?
>
> i develop my plugins only with jEdit and javac. for debugging, i use the
> org.gjt.sp.util.Log package. for example:
>
> Log.log(Log.DEBUG, XMode.class, "Error message");
>
> or
>
> catch (Exception e)
> {
> Log.log(Log.ERROR, this, e);
> }
>
> you can control which log messages appear on standard err by specifying a
> number from 0 to 9 on the jEdit command line. all messages go into the
> jEdit activity log.
>
> sometimes, i also use the BeanShell plugin to poke around at objects in
> jEdit's runtime environment. this is really cool because you can track
> down elusive bugs without having to restart jEdit by simply hacking up a
> simple BeanShell script. you can even use the aforementioned Log package
> through BeanShell, although i'm not sure how Exception handling in
> BeanShell works (if at all).
>
> -md
>
>
> --
> -----------------------------------------------
> jEdit Developers' List
> jEd...@li...
> http://lists.sourceforge.net/mailman/listinfo/jedit-devel