On Thu, Apr 10, 2008 at 4:20 AM, Ville M. Vainio <[EMAIL PROTECTED]> wrote:
> > Here's a stopgap measure to survive 2 people editing the same .leo > file, with very little coding I'm not sure I understand the problem you are trying to solve. bzr will warn about conflicts in .leo files. In a collaborative environment, all data should be in thin derived files. The "reference" .leo files hardly ever change, the corresponding local .leo files can have whatever people want. Perhaps more importantly, Leo's compare-leo-outlines command was designed to handle cvs conflicts. It compares the present outline with another, and creates clones of all inserted, deleted and changed nodes. Might this be a good starting point for you? 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 -~----------~----~----~----~------~----~------~--~---
