Sounds great! -hehe- And on top of that it will work similar to how internet browsers work (they open new links in a new tab) which is more intuitive for people since everybody uses them. Moreover, support for session tracking and restoring becomes an instant addition since just by oppening all the @path leo nodes under a "session" node we can restore our session!
On Monday, May 27, 2013 6:05:44 PM UTC+2, Edward K. Ream wrote: > > On Mon, May 27, 2013 at 9:49 AM, Terry Brown <[email protected]<javascript:> > > wrote: > > >> > Yes. I'm not sure how this could be changed so as to use an >> already-open >> > Leo. >> >> The leoserver plugin lets you do this. Here's my wrapper for loading >> a .leo file from the command line into the existing Leo instance: >> > > [snip] > > So you'd need to associate .leo files with this python code... and it >> would also need to do something smart when Leo wasn't already running. >> >> This only works with the leoserver plugin running of course. >> > > Thanks for this. I'm wondering, given that our focus is on installation > issues, whether the leoserver plugin should be promoted into Leo's core, so > that the standard install would "just work" in the way that Fidel would > like. > > Comments? > > 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 http://groups.google.com/group/leo-editor?hl=en-US. For more options, visit https://groups.google.com/groups/opt_out.
