> P.S. In your particular situation, I would suggest, if at all > possible, that you make complete external files, rather than clones, > to be the "units of sharing". That way there is only one copy of the > data, so if you change that data outside of Leo all clones of (parts > of) that data will be in synch the next time you open Leo. > > EKR
Oh. I thought one of the major reasons for clones was to be able to "boiler plate" common content across many files. Examples might include copyright notices, written by _____, code functions that get re-used a lot and so on. Is this an incorrect, or at least inadvisable, use of clones? -- -matt -- 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.
