On Jan 21, 5:15 am, "Edward K. Ream" <[email protected]> wrote:
> As you and Ville indirectly suggest, I agree that external files > containing @all directives should never win a "clone war". The more I think of this, the more I think that this will solve most, if not all clone problems. The "clone resolution" algorithm becomes simply: 1. Data in external files overrides data in .leo files. 2. Data in external files *not* containing an @all directive overrides data in external files containing an @all directive. These rules should tame clones in leoProjects.txt and leoToDo.txt. I suspect that is all that will be needed in practice. The great advantage of this scheme is that moots the need for more complex error recovery. Only time will tell whether this is truly enough, but I have my hopes. I plan to implement these rules today. Edward P.S. I plan to add leoProjects.txt back to the bzr repository. This file contains useful data, and furthermore it is an ongoing practical test of Leo's ability to handle clones. As I said a few days ago, banning clones would be cowardly. EKR -- 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.
