I haven't looked at the jEdit source, but the whole *purpose* of the context loader is to avoid having to have explicit configuration APIs for class loaders. It sounds like it would make more sense to patch jEdit to set the context loader appropriately
That being said, editor integration is a big win, so if Clojure has to do something warty to enable this I guess I'll just hold my nose. > I am working on a Clojure plugin for jEdit. Currently you can use > Clojure source as jEdit macros and evaluate source directly from a > buffer. Next step is the incorporation of a REPL. > > The first try proved to be a bit more troublesome than I had expected. > Apart from me being wrong footed by jEdit´s idiosyncratic use of class > loaders, the initialisation of Clojure did not really help. > > Currently the RT class contains a static initializer block which calls > DoInit. From there the Clojure "boot files" (boot.clj and friends) are > loaded from the Clojure jar. Thing is that Clojure uses the thread´s > context class loader when initially loading these resources. And as > jEdit loads a plugin from within a thread (the AWT event thread) which > does not have the correct class loader set, Clojure could not find > its own boot scripts. > > Ideally Clojure should allow the configuration of the initial class > loader, for example through binding the Compiler.LOADER Var. If > relevant, can I send in a patch? > > Alternatively a quick and workable solution is by having Clojure > initialized from within a back ground thread which has the proper > context class loader set. > > Regards, > > Iwan van der Kleijn > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
