On Tue, Dec 3, 2013 at 3:10 PM, SegundoBob <[email protected]> wrote:
> I don't understand what Leo-Editor is doing in this case. I don't know > Edward K. Ream's intentions in this case. > The intention for "clone wars" is that the last clone loaded by Leo "wins". So where you drag a clone in a .leo file can and does matter. If you change data in an external file, then it's good to move clones before any @file nodes containing them. Or just delete the clones. In theory, I could get bitten by this problem myself, but I seldom do because: 1. I usually delete clones once a project is finished. 2. When I work on a project, I'm the only one working on the clones, so warring clones don't happen. (bzr pulls won't change the clones). 3. If I do save clones long-term, I move them into @file leoNotes.py, which occurs (on purpose!) in leoPy.leo before all @file nodes containing those clones. HTH. 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. For more options, visit https://groups.google.com/groups/opt_out.
