> > It is very cool, and your steps didn't quite work for me. I'm using pyzo > 4.10.2 on Windows. For one thing, I don't even have an F5 command. Here is > what I did: >
Oh! F5 is menu "*Run >> Execute file*" which might also be bound to Ctrl-E. It's the conceptual equivalent to Leo's "*Run current node tree as script*", Ctrl-B. Thanks for adding another working recipe. Beyond this, I don't know much about what you can do with them so far. but > it's very cool ... > Anything you do in the interactive shell becomes part of the Workspace. I use it most to look at what my variables etc. actually turn into (which can be quite different from what I *think* they are!). So if I have this function in a script (that I have opened and run in Pyzo): def get_leo_libpath(): import leo return leo.__path__[0] and assign it, either in the script or in the interactive shell: x = get_leo_libpath() This variable and it's value are now visible in the Workspace immediately. This means I don't need to sprinkle print(x) when I'm trying to understand what's happening. This is probably a narrow use of it's actual feature set. Using it this way for all of Leo as a running app might not be that practical, for instance whatever you do in the running Leo GUI won't show up in Pyzo's workspace (I don't think anyway, I might be wrong about that). I'm finding it useful right at the moment because it shows me all the Leo parts that loaded and available, and inside what modules. (Which is a different picture than just scanning 'leo/core/...' for .py files, that may or not have been called yet.) -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/1d8afc8c-79ce-4306-9346-3e8724e1c3cc%40googlegroups.com.
