Found what I was looking for, http://leoeditor.com/FAQ.html#leo-in-shared-environments. Does anyone have other tips along the same lines to share?
On Sat, Oct 21, 2017 at 1:07 PM, Matt Wilkie <[email protected]> wrote: > Hi Folks, > > I'm getting back into Leo after some time away and need a refresher on how > to best structure my files and folders, particularly with how to work with > source code version control systems and other collaborators who don't use > Leo. > > My old workbooks are filled with broken @path references and I want to > ensure this go 'round doesn't lead to the same end! As I study the pattern > of brokenness, most stem from me keeping my .leo files outside of the > version controlled repos. This is a kindness to collaborators, no need for > them to be subjected to a stream of commit noise when I'm just muttering to > myself. > > The table of contents <http://leoeditor.com/leo_toc.html> doesn't help > direct my quest ("Leo with other programs" would be a good place for a > future doc of this type) . Where should I start? > > Thanks! > > Matt > -- 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
