Interesting... I first noticed the effect while using Leo snapshot 201004120253 (ActivePython 3.1 32bit, pyqt 4.7.2, Windows 7 64bit w/8gb ram, NTFS file system), but switching back to 4.7.1 final didn't alleviate the issue. The way I've been using Leo is to create a new node for my coding project, flesh out my code there, and when I was ready to test I would create the @shadow node, and clone all the nodes from my project node over to the shadow. Initially, every time I would open a .leo file all the line endings would change from \r\n to \r\r\n. The side effect would be Leo reporting an uncached update, and all the cloned nodes would no longer be marked as clones. They would instead be identical copies, except all the line endings were transformed. Changes to these unmarked nodes would not update their respective copies in my project node. I assumed this to be a problem with my line endings specification, so I tried troubleshooting from that perspective. What finally ended up working for me was upgrading to the snapshot, switching my line endings to newline, and then using the Find/Replace to traverse my outline replacing all instances of \r\r\n with \n. Everything was fine until a coworker made a small change in one of my @shadow'ed files. Leo attempted to read the file, delinked all the cloned nodes, and replaced all the line endings with \r\r\n. At this point, I wondered if the problem may have been the 32bit python on 64bit windows situation, so I installed VMWare and loaded up Leo inside of a Ubuntu Linux (Linux ubu1004 2.6.32-22-generic #33- Ubuntu SMP Wed Apr 28 13:27:30 UTC 2010 i686 GNU/Linux, Python 2.6.5) virtual machine. The problem with the line endings getting munged has disappeared, but instead updates to the @shadow'ed files randomly delink when the file is refreshed from disk. Sometimes simply closing and reopening Leo resolves the issue, other times not.
I'm really more of a functional programming guy.. I can read Python enough to understand what it's doing, but not enough to track down the origin of this behavior. Any ideas? Alex On May 14, 4:39 pm, "Edward K. Ream" <[email protected]> wrote: > On Fri, May 14, 2010 at 4:41 PM, a'Lex Mumme <[email protected]> wrote: > > Hi everyone, > > Long time listener, first time caller. > > Is it the expected outcome that when external changes are detected to > > files created by @shadow nodes, the clones that are under that node > > all de-link? > > Iirc, the @shadow update algorithm never deletes sentinels, so clones > should be preserved. > > 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 > athttp://groups.google.com/group/leo-editor?hl=en. -- 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.
