On Thu, 15 Dec 2011 11:24:43 -0500 "Edward K. Ream" <[email protected]> wrote:
> I am going to study leoremove first. It seems like a more general > solution than low-level signals, however wrapped by Python. I think that's true - but if it's going to be the mechanism for tracking running Leo's it would need to be enabled by default, which is ok. Currently starting Leo again with leoremote enabled in both instances tends to mess up the leoremote functions, you seem to end up with neither Leo responding. But of course this new code would address that. leoremote is the basis for my scripts `led`, `lo`, and `sn`, which, from the command line, load a file into the running Leo, load an outline into the running Leo, and create a stickynote in the running Leo. They're either on the wiki or in the contrib branch. Cheers -Terry -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
