On Mon, 27 Aug 2018 10:55:13 -0700 (PDT) Phil <phil.s....@gmail.com> wrote:
> Thanks for that, it's helpful. But the notion of a reference file > begs the question of who maintains *that* file. In my project, both > my partner and I are continually creating new content, which means > that we would both need to make changes to the reference file. This > impedes the efficiency that we could achieve by working concurrently > - we would instead need to take turns updating the reference file. > > Maybe I'm still missing something? I'd do something like this: - each have your own Leo file, which is your personal view of the project, so the fact they're different might be quite convenient. - use something like the active_path plugin (or a script / button whatever) to make adding references to new external files trivial. In the case of the active_path plugin you just double click the directory node to show unloaded files in that directory. - if you want to backup you personal Leo files in the shared git repo. you could, in some folder like .../etc/usr/phil/SomeProject.leo and .../etc/usr/philscollaborator/TheProject.leo - or you could see that perhaps the .leo file is surprisingly low value, depending on what you put in it, the low chance of losing it and the ease of recreating it with the above active_path etc. approach might make it not worth backing up - if your storing to do items or using @clean with edited node arrangements or similar you will want to back up the .leo file, either in the shared git repo. or some other way, perhaps your systems regular nightly backup ;-) Cheers -Terry > On Monday, August 27, 2018 at 10:42:37 AM UTC-5, Edward K. Ream wrote: > > > On Mon, Aug 27, 2018 at 10:19 AM Phil <phil....@gmail.com > > <javascript:>> wrote: > > > >> I am currently collaborating on a project with one other person, > >> using Leo and Git. In addition to committing derived files to Git, > >> we have also been committing the Leo file itself. We have had some > >> occasional problems (a corrupted Leo file, mainly), making me > >> think that we should *not* put the Leo file in Git - but maybe > >> it's something *we're* doing wrong, and not Leo. > >> > >> What is the recommended way to use Leo in this scenario? > > > > There are several FAQ entries <http://leoeditor.com/FAQ.html#id61>. > > Let me know if you have questions or comments. > > > > 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 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.
