On Sunday, August 4, 2019 at 1:24:05 PM UTC-5, Edward K. Ream wrote: I'm going to sleep on these problems for a day or three. It's not clear > whether these problems apply to org mode or vimoutline. >
The original Aha still stands: there is no need to transliterate gobs of Leo's python code into elisp or vimscript. Alas, the Aha isn't nearly so "momentous" as I first thought. Embedding Leo into another program likely will founder for design reasons, regardless of code tricks. I have abandoned, for now, the idea of embedding Leo into pyzo. Imo, pyzo isn't a good fit for Leo. Instead, I have begun work on using pyzo's features in Leo <https://github.com/leo-editor/leo-editor/issues?q=is%3Aissue+milestone%3A6.1+is%3Aopen+label%3Apyzo>. The pyzo branch contains a copy of all of pyzo's sources in leo/external/pyzo. The following .bat file runs pyzo properly: python <path to>\leo\external\pyzo\__main__.py %* This shows that there are no gotchas involved in "relocating" the pyzo sources. The interesting part will be to import only the needed parts of pyzo from leo/external/pyzo, without loading pyzo's main window. 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/3f95863e-1017-4002-a318-2e2ed424017a%40googlegroups.com.
