> Rev a627fcc ensures that @cloned nodes to two different paths will both > be written. The fix was entirely straightforward and all unit tests pass. > But... >
Thank you Edward! > > *Warning* > > This rev changes corresponding code in at.readAll, but here the results > are kinda like rearranging chairs on the Titanic :-) > > All will be well as long as both external files contain exactly the same > code, but Leo does not detect if the two files are different, say if one > has been changed with another editor. Afaik, Leo has *never *been able to > detect changes between two different *cloned *nodes with the same gnx. > > What will happen is that one of the clones will "win". Before today, the > *first* read node will win. Now, the *last* cloned node will win. > > In short, you are asking for trouble using two cloned @clean nodes (or any > other kind of @<file> node). This has always been true, and will likely > remain so forever. > > Ok, that makes sense to me, and I will keep it in mind in the future. As a mostly sole developer writing code almost entirely using Leo, I don't usually modify files outside of Leo, so I wouldn't expect problems. Thanks again! Phil -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
