> It appears that my Startup.bsh script is not being called at jEdit
> startup. This is the first time I've tried the new 3.2 code so I don't
> know how long this has been broken (I assume it's broken, but let me
> know if I'm wrong.)
> I know it is not being executed because I have some methods defined in
> my Startup.bsh file and they aren't being defined. I also added an
> Activity Log statement to the top of the script and it is not getting
> Jonathan Carlson
You may have missed a change in the startup script protocol as 3.2 evolved.
To enable multiple startup scripts, the application now runs any .bsh file
in the /startup subdirectories of both the jEdit installation directory and
the user's settings directory. A startup script can be placed in either
location and need not be called "startup.bsh". Such a script placed in the
/macros directory will no longer be executed at startup.