On Thu, Dec 12, 2013 at 8:18 PM, Largo84 <[email protected]> wrote: > Advance apology if this has already been considered and discarded as > impractical, stupid or whatever (since I'm not a programmer) >
It's not a stupid idea, but it won't work. The problem is keeping the two sets of files in synch. The best approximation I have ever come up with is to commit (transmit) files with sentinels, hand then have bzr/bit/etc automatically strip the sentinels for non-Leo users. But this really isn't satisfactory: non-Leo users really can't be expected to do *anything* to support Leo, and this scheme requires bzr hooks for all non-Leo users. Things would be different if Apple's old file scheme (all files have a resource fork) were industry standard. Then the "sentinels" could be part of the resource fork. But even so, non-Leo users aren't going to properly update the sentinels. In short, making @auto work well is the only hope there is in practice. This takes *all* burden off of non-Leo users, requires no infrastructure changes at all for Leo users and non-Leo users alike, and completely eliminates the need for sentinels. Edward -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
