On Wed, Jul 1, 2009 at 7:04 PM, Ville M. Vainio<[email protected]> wrote:
> If the clones are not siblings, they are written correctly. > >> Is this a feature or a bug? If it's a feature, what's the reason or >> benefit? > > Interesting question, I see no reason for this myself (why are > siblings special in this matter?) In Code-->Core classes-->@thin leoAtFile.py-->at.Writing-->Writing 4.x-->writing code lines...-->@all-->putAtAllChild QQQ @ This code puts only the first of two or more cloned siblings, preceding the clone with an @clone n sentinel. This is a debatable choice: the cloned tree appears only once in the derived file. This should be benign; the text created by @all is likely to be used only for recreating the outline in Leo. The representation in the derived file doesn't matter much. @c QQQ However, the same (misguided?) check is done at Code-->Core classes-->@thin leoAtFile.py-->at.Writing-->Writing 4.x-->writing code lines...-->@others-->putAtOthersChild You could try eliminating various calls in for scanForClonedSibs in the source and seeing if the world breaks - probably not. That being said, I find the cloned sibs thing in Code-->Core classes-->@thin leoAtFile.py-->at.Reading-->Reading (4.x)-->createThinChild4 Quite baffling myself. -- 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 [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 -~----------~----~----~----~------~----~------~--~---
