My fix pushed to devel with 016867f <https://github.com/leo-editor/leo-editor/commit/016867f5ade5da6796397ab4705287bf8b8f336a> .
Things I learned exploring this issue: - Leo's *g *global module contains the python *os*, *sys*, and *subprocess *modules, so they don't need to be initialized (imported) in order to use them. - g.app.leoDir == *leo-editor/leo*, and g.app.loadDir == *leo-editor/leo/core*. - *./leo/core/runLeo.py* is the real work horse for starting Leo. (I've often been confused about just how/where Leo is started.) - Leo needs to be restarted in order to pick up changes in this core file (probably true generally) - I really am able to identify, locate and fix a bug in Leo within an area I have no previous experience in! (At least once anyway. ;-) What I still need to learn: how to write and run Leo unit tests. -matt -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/45d728f3-ab72-41e2-8253-891a61eb3e2f%40googlegroups.com.
