Thanks for the advice, Robert.
I've tried using jEditLanucher with sone degree of success - I was wondering if anyone knew why the follong process does'nt work completely...

Calling the jEditLancher (application executable jedit.exe) like this:

jedit -run=test.bsh

With a beanshell script TEST.BSH as follows:

//--------------
import org.gjt.sp.jedit.*;
import org.gjt.sp.util.*;
import org.gjt.sp.jedit.gui.OptionsDialog;
import org.gjt.sp.jedit.msg.*;
import java.io.*;
import javax.swing.*;
import java.awt.*;
import java.awt.event.*;
import errorlist.*;
import java.util.*;
import gnu.regexp.*;
import console.*;

DefaultErrorSource errsrc;
void run()
{
errsrc = new DefaultErrorSource("Whatever"); ErrorSource.registerErrorSource(errsrc);

errsrc.clear();

errsrc.addError(ErrorSource.ERROR, "c:\\test.c",1,0,0,"Oh dear!");

ErrorSource.unregisterErrorSource(errsrc);
errsrc = null;
}
run();
//--------------

Will run without any reported error, and sure enough, an error message is logged in the ErrorList dialog as expected. However, running the same script again results in another IDENTICAL error message being added - in other words the errsrc.clear() directive is not working. In fact, using the jEdit menu option to clear the ErrorList does not remove these messages either!

A possoble clue to the problem is given when I change the script to this:

errsrc.addError(ErrorSource.ERROR, "c:\\test.c",3,0,0,"Oh my!");
errsrc.addError(ErrorSource.ERROR, "c:\\test.c",2,0,0,"Ooops!");
errsrc.addError(ErrorSource.ERROR, "c:\\test.c",3,0,0,"Not again!");
errsrc.clear();
errsrc.addError(ErrorSource.ERROR, "c:\\test.c",1,0,0,"Oh dear!");

In this case I only get the LAST error message, so in other words the clear() methos works within the scope of this BSH script.

Does anyone know whats going wrong? Further, how do I use the addError() method fron an invoked BSH script in the same way as a plugin does?

Hope someone can help!
Paul

I guess that You have to deal with the jEditLauncher (www.rutherfurd.net/jEdit/launcher).

From the user's guide: " The core of the jEditLauncher package is a COM component that can communicate with the EditServer.. ..the functions of jEditLauncher are available .. using the Win32::OLE package"

It seems that You can can control jEdit only by Beanshell scripts with LauncherObject.EvalScript("String_with_BeanshellStatements"). Robert