On Thu, Jun 25, 2009 at 2:18 PM, Edward K. Ream<edream...@gmail.com> wrote:
> I don't think Leo can, or should, do anything more in this area. Talked about this recently... To quote the Zen (tm), "In the face of ambiguity, refuse the temptation to guess." Simply, I don't trust any "heuristic" on this, e.g. file timestamp doesn't help much (suppose you just pulled leoNotes.txt from bzr). Order in tree structure isn't that trustworthy either. I'm suspicious about some interactions with the hashcaching, for example. The thing leo needs to do is really ask the user which node to keep, when conflicting versions of same node are read. This interrupts the loading for a second, but the cost of not doing that is possible data loss. As importantly, the user needs to be very aware of the conflicts like this, it's easy to overlook these and allow data to be lost silently in the background. -- Ville M. Vainio http://tinyurl.com/vainio --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
