On Tuesday, April 11, 2017 at 5:57:04 AM UTC-5, Edward K. Ream wrote: > There is a better workaround, namely, use a separate local leoPy.leo for each branch: [big snip]
> I'll be using (testing) this today. All went very well, without any surprises at all. This workaround is probably good enough for the foreseeable future. This is a good thing, because fixing #385 <https://github.com/leo-editor/leo-editor/issues/385> could be tricky. My master-leoPy.leo will never contain clones. This *might* sidestep #385 issues completely. It will certainly minimize those issues. Edward 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 leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
