On Tue, Jul 12, 2011 at 5:57 AM, Josef <[email protected]> wrote: > >> Why not? > > Not sure, perhaps I just need to change my working style a bit. > > I have a lot of information that I keep outside the @file nodes. > Documentation for example, which is not directly linked with the code. > I see you yourself are sharing information via Leo files, that are not > just reference files (the LeoDocs.Leo file for example - although this > is probably a file your are mostly editing alone).
Yes. The general idea is to keep the .leo file constant, except for infrequent updates. It remains to be seen how easy sharing files like leoNotes.txt would actually be. As you say, I am typically the only one that touches this file. However, bzr should be able to handle updates to this file... > But one could put > all the content into @file nodes, at the disadvantage of having > multiple files instead of having everything nicely in one single Leo > file. I think this is the only way in shared environments. You can also use @auto instead of @file, but then you lose the ability to clone nodes persistently. 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.
