Re: Not-clones that act like clones

Thanks, Edward. However, I don't understand why it matters that html and css 'lack functions'. Imo, in your use case it's ok to use cross-file clones. The normal rules do > not apply because html and css lack functions. > > Thanks to everyone who 'weighed in' with comments; it appears that in

Running the pyzo file browser from any Leo node

Here is the Leonine script: '''Instantiate the pyzo file browser inside Leo.''' # # Part 1: The import shim. import pyzo.core.menu as menu # Needed to import pyzoFileBrowser. assert menu import pyzo.tools.pyzoFileBrowser as fb from pyzo.core.main import loadIcons # # Part 2: Instantiate the

Re: Not-clones that act like clones

As I understand it, using cross-file clones is somewhat safer if the clones are *underneath* @file/@clean nodes and not the @file nodes themselves. (I got myself into a pickle before by cloning @file nodes under different @path parents; don't remember the specifics now). Matt -- You

Re: ENB: strategy for moving pyzo code into Leo

> > 3. I'll ignore potential distribution problems during prototyping. For > example, I'll assume that Leo can use pygments. As with pyzo, Leo 6.0 will > require Python 3. > Note for readers: Pyzo requires py3 for itself, but is perfectly happy being an IDE for py27, including running an

Re: How to run code (in any language) in external processes

> > It's dead easy to run code in an external process, so that Leo doesn't > hang. Just use g.execute_shell_commands. > this is timely! thanks. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop

Re: ENB: pyzo progress report

On Sunday, March 10, 2019 at 8:14:53 AM UTC-5, Edward K. Ream wrote: > Pyzo's import structure seems unlikely to hinder using any of the code that I want to move into Leo. As mentioned in the "Startup" section, there subtle differences between running pyzo.exe and running pyzo from a script.

Re: Not-clones that act like clones

On Sat, Mar 9, 2019 at 11:00 AM Rob wrote: > Suppose I have a xxx.leo file in which I write multiple web pages (or > other document types, same question). > >- Each document is a separate @file (or @clean) external file. >- Inside each web page are sections (nodes with or without

Re: bug in JSON scanner?

Hi Edward well, after saving the @auto file the node gets restored next time, but the content of the file is not what you see in the node (body), but a special JSON file, which describes the node, it's children, even the uA's etc. Such a file is of course useless when I want to edit an

ENB: pyzo progress report

Moving pyzo features into Leo promises to be easier than expected. This Engineering Notebook post discusses recent good news. *pyzo.leo* This has already been well worth the effort required to create. You can find it in my clone of pyzo . pyzo.leo allows