On Wed, Apr 23, 2008 at 10:19 PM, Satheesh Babu Vattekkat <[EMAIL PROTECTED]> wrote:
> > I am wondering if I can "include" a remote node from > another file within my stuff.leo. Then, I do not need to have multiple leo > windows open and for documents that are getting shared across folks, I can > put my own thoughts "around" what is shared. The short answer is "no". The reasons have to do with guaranteeing data consistency. You could try to put @thin x in several .leo files, but I do not recommend that: it would be too easy to lose data because of the "multiple update" problem. That is, if you change x in two different .leo files, you will lose the changes that you save first. A plugin could try to set a file lock, so that only one version of x could be open at any time, but that might create other annoyances. So absent truly significant new invention, by far the easiest way is to put shared data in their own .leo file, as presumably you do now. > > > I guess something like @leo node is what I am looking for :-) This has been discussed many times in the past. I don't know how to do it safely, and I'm not interested in it for that reason. There are *many* behind-the-scenes issues in Leo regarding data consistency and error recovery. These evolved over a period of several years, and the solutions, while fairly simple now, did not come easily. And again, the multiple-update problem appears, this time in a slightly different guise. 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 -~----------~----~----~----~------~----~------~--~---
