My workflow consists of a bzr directory tree, a Leo file at the top contains @shadow nodes for the files I'm working on.
I edit this tree from a few different boxes, my bzr push and bzr pull are used to sync between the boxes. When I pull, the .py file and the .leo file are updated, not the shadow files, my .bzrignore file includes .leo_shadow I just did a pull and found that some changes had been lost. I did find -path "*/.leo_shadow/*" -delete which deletes all shadow files I then deleted the Top.leo file (containing the @shadow nodes) and did bzr revert Top.leo Now the changes are intact. IOW, it seems the precedence had been .leo_shadow/xsource.py -> Leo -> source.py instead of source.py -> Leo -> .leo_shadow/xsource.py I expect that @shadow land is on shifting sand, I should periodically purge the .leo_shadow files until things settle. However, correct @shadow behaviour is important and I wish my testing could provide useful data for debugging. How about a shadow.log file which Leo told what it thought of the relationship between the node, file and shadow? It might provide useful clues. Thanks, Kent PS prior to purging shadow files, I also had some nodes in the Leo file containing Python code which wasn't being chunked. The chunking returned after the purge. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
