I just had a look at leoGuiPluginsRef.leo and it contains a lot more than just @file nodes: @chapters, @settings, commented out buttons etc.
so, is the statement: Ref files should contain nothing but @file, @auto and @shadow nodes the whole truth? I also used (successfully) clones in my leo files, where I simply cloned the *whole* @file node. When writing such nodes, I get warnings that the node has not changed (of course, the second write to the cloned file is the same as the first), but otherwise it works - but I was the only one working on the Leo file, and one should never clone part of an @file node. A cloned part of an @file node should only be stored inside a single @file node, and nowhere else, but that is of course not simple to enforce (just imagine, someone puts the same clone inside two different @file nodes). For the same reason, hard links cannot span multiple volumes. I think, the best would be if Leo would not allow clones beneath @file nodes. When starting to share Leo files it will be difficult to explain all these limitations to new users. They should be able to do anything Leo allows them to do, without running into merging problems. Perhaps this could be solved with a merge tool for Leo files? - Josef On Jul 7, 10:07 am, Josef <joe...@gmx.net> wrote: > > You won't have conflicts in the .leo files provided that you use > > "reference" .leo files, as we do in the Leo project itself. See the > > FAQ:http://webpages.charter.net/edreamleo/FAQ.html#leo-in-shared-environm... > > So, I cannot share my non-reference files - that is a serious > limitation. It is these non-reference Leo files, where the interesting > stuff is. I need to share these. I want my colleagues to be able to > see my notes, and the tree. I also keep some data in Leo files, which > I cannot easily move to @file nodes. I also want my colleagues to be > able to use my scripts, which are embedded in Leo files. > > As an interim solution I will lock any (non-reference) Leo files in > SVN, thereby prohibiting any parallel work on them, but this is of > course not entirely satisfying. > > P.S.: the "bzr repository" link in the FAQ link above seems broken. -- 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.
