I dislike having multiple editors/IDEs open because it is often messy and the "integrated" component of IDE gets lost.
I'm not implying that you do more work; it is your Leo, we just use it. I'm not optimistic that users would see this as a "good" or "clean" solution to having shell and file browser features available to them. I am, however, implying that your Doh/Aha moment might be a personal one and that the desire for the stated features to be integrated *within* Leo will not go away because of it. That said thank you for the recent work, very much appreciated. On Tuesday, June 18, 2019 at 2:28:51 AM UTC-4, Edward K. Ream wrote: > > Leo 6.1 supposedly would integrate pyzo features into Leo. See this page. > <https://github.com/leo-editor/leo-editor/issues?q=is%3Aissue+milestone%3A6.1+is%3Aopen+label%3Apyzo> > > In fact, doing so would be foolish and unnecessary, as I shall now explain. > > *Doh: Read the documentation, Luke* > > A few days ago I had a sickening Doh! moment. I have done extensive > code-level prototyping of pyzo integration without having a clear idea of > what pyzo does! I'm talking about the *basics*, covered in the pyzo intro > <https://pyzo.org/pyzo_intro.html>, configuring shells > <https://pyzo.org/shellconfig.html> and interactive vs script mode > <https://pyzo.org/interactive_vs_script.html>. > > From the pyzo intro: "Shells run in a sub-process, such that when it is > busy, Pyzo itself stays responsive, allowing you to keep coding and even > run code in another shell." > > This explains why pyzo uses yoton, and the related complexity. yoton > allows pyzo to show results in the "Workspace", "History Viewer" and > "Shell" areas, while the actual computation happens in an external process. > > So far, so good. What are the implications? > > My first thought was that Leo could easily adapt the Ctrl-B logic to run > code in an external process. But just a bit more thought shows that that > won't work. *Scripts run in an external environment can't be Leonine*. > They could be given access to c, g and p, but they could not control Leo > without heroic measures. > > > *Doh: Pyzo can run alongside Leo* > > Yesterday I saw this clearly for the first time. It was another > sickeningly obvious "revelation". > > Pyzo does a great job of showing and updating external files. So anyone > can get the benefits of both Leo and Pyzo *right now* as follows: > > 1. Use Leo to create and update external files, as usual. > 2. Use pyzo to open files and run shells, as desired. > > In short, adding pyzo's features to Leo would be really really stupid. > > *Summary* > > Anyone can get the benefits of Leo and pyzo by running them side by side. > Doh! > > I shall not add pyzo's major features to Leo. Not in 6.1. Not ever. > > Suddenly, Leo looks finished as well as complete :-) It's time to > investigate new directions for Leo with more playful prototypes. > > All comments welcome and encouraged. > > 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 https://groups.google.com/group/leo-editor. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/3faacace-ddbf-4f91-8c17-86fec0d0e196%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
