> One can imagine situations in which the developers that don't use Leo > are not hostile to having Leo's sentinels in the group's files. In > this case, @file can be used and there are no problems.
In my company, the others don't mind the sentinels, but since I use leo as a storage for data which *inherently* needs or benefits from a tree representation, this cannot be conveyed to others via the @file nodes alone, but I must start sharing data with others via Leo files (and the colleagues are excited about Leo). It is not always convenient to do this only with reference files. Unfortunately, that is exactly where the problems start, because I understand from the recent conversation here, that generic Leo files do not work well with automatic (text based) merging. - Josef -- 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.
