RGK: Discovery Notebook (feel free to ignore) Perhaps it might help others struggling to learn how Leo's core works; will post random thoughts as I try to figure this out, dead ends and all.
1. After finding the code for g.extractExecutableString(c, p, s) in LeoPyRef.leo (found in Leo's core directory) it seems to me that I'm probably not going about this the right way (even though it sorta worked). 2. The call to g. getScript seems to be intended to only work with python scripts (based on code from #1 above). As I understand the code (which I don't), no explicit @language directive forces python as the 'assumed' language, while any other explicit @language directive will cause subsequent lines to be ignored (this is exactly what I observe). 3. I don't see how altering that code block would work w/o screwing up the whole script mechanism (don't want to go there). 4. So, my initial thought is to find a different way to retrieve the node and subtree expansion contents besides calling g.getScript. 5. First guess would be to find something in Leo's write to file code. Haven't found anything yet, will continue looking. Rob... -- 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
