On Jul 6, 8:10 am, "Edward K. Ream" <[email protected]> wrote:
> You won't have conflicts in the .leo files provided that you use > "reference" .leo files, as we do in the Leo project itself. See the > FAQ:http://webpages.charter.net/edreamleo/FAQ.html#leo-in-shared-environm... This is perhaps a too-glib response. In some sense Leo's "real" major failing is that it makes collaboration just a bit harder that it otherwise would be. This effect is masked a bit here because all of Leo's developers use Leo and bzr. The "acid test" is whether Leo can be used by some, but not all, developers on a significant project. At present, the best that can be done in such situations is to use @auto or (maybe) @shadow for the group's files. This is far from optimal because clones don't "survive" in @auto. Partly as a result of your question I have been thinking, once again, of re-imagining what Leo is. I'll be saying more about this in another post. Edward -- 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.
