On Oct 1, 2:35 pm, "Edward K. Ream" <edream...@gmail.com> wrote: > Using a common .leo files should be easy enough: just put > everything that could change in an @thin node.
I was hoping for a lazy automated solution. Putting changing parts into @thin nodes is a good idea, but adding a new source file (as one more @thin node) still changes the outline. I've noticed that if I modify an outline externally, leo warns me about changed content when I'm trying to save it, but that's a different story. I was hoping I could do "vcs_app update revision_id" in a terminal, then switch to leo window and leo would reload the changed @thin nodes or the whole outline if needed. Maybe there's at least some leo API function which I could stick into a button and explicitly force a full reload of the current outline (without having to close and reopen leo) every time I update the workspace to another revision? Another way would probably be to use @shadow, because I remember leo being able to detect external changes for them and refresh the tree. -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@googlegroups.com. To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
