On Thu, Jan 31, 2013 at 7:18 AM, Jacob Peck wrote: > [exec(g.findTestScript(c,whatever))] is crazy powerful, just like the rest of Leo. I'll probably end up doing it this way.
Yes. There is nothing like Leo for scripting. > One other way I found of doing it, after I posted my question, seems very dirty and hacky, but it works. I have a @script node that has the common code, and using the leoPlugin hooks, adds my common functions to c, giving me a place to call them from. But this requires scripting to be enabled, modifications to c, etc. The down side of "crazy powerful" is that .leo files with @script nodes enabled are *very* dangerous for the unwary. That's why @script nodes must always be disabled by default, but that hardly helps if the .leo files themselves enable @script nodes! As I write this, it seems to me that the one and *only* place that @script nodes should be *allowed* to be enabled is in myLeoSettings.leo. But at present that "lock on the H-Bomb" does not exist. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
