On Tue, Dec 20, 2011 at 10:19 AM, HansBKK <[email protected]> wrote: > given a single user, and never looking at the external files generated > @shadow and @thin are functionally equivalent.
@thin "carries" structural information in the actual external file. @shadow carries structure in the private file. The difference is subtle, but important. When you do a bzr pull on a node containing sentinels you get the *new* structure from the push. When you do a bzr pull on an public @shadow file you get the new data but *not* any new structure: the @shadow update algorithm "invents" a way to incorporate the new data using the *old* structure. In general, this will be a lot less convenient than using files with sentinels. > But I thought one of the main points of your OP (switching over to the > "imagined possible" reality) was the ability to store (almost?) everything > related to the content, outside of the individual user's Leo file, in > particular the "views" created by that user. I am no longer sure what the original intention was ;-) 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 at http://groups.google.com/group/leo-editor?hl=en.
