On Tue, Jun 23, 2009 at 10:55 PM, thyrsus <sschae...@acm.org> wrote: > > I do a good bit of clones getting expanded into multiple locations, > and it works well for me. Important things to remember: > > * If you're using @thin, it means the .leo file is thin, and the > derived file is fat.
Okiedokie, I'll move the doc-bits in question out of the .leo file into derived files. :) > > > * If you've got nodes cloned into multiple @thin or @file locations, > and their contents gets changed outside of Leo, then the last version > encountered during the reading of the derived files wins. Not a huge deal, the clone nodes are shared boilerplate and won't get touched for much of anything. > > > * If the sentinels are damaged outside of Leo, Leo can sometimes get > confused -- more often with @file than with @thin. I'm just going to make Leo a requirement for editing the code. ;) > > > > * Unless your versioning system is extremely short of disk space, tell > your versioning system that the .leo file is a binary. Trying to do > reconciliations between XML files is close to impossible except in the > very most trivial cases. I've only done it successfully twice; you're > almost always better off abandoning your changes, checking out from a > known coherent version, and redoing the work from there. Good idea. > > > Good luck, > > - Stephen > > <quote snipped> > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-editor@googlegroups.com To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en -~----------~----~----~----~------~----~------~--~---
