>
> Similarly, the open-leo-py-ref-leo command makes it significantly easier
> to keep LeoPyRef.leo in sync with my personal leoPy.leo files. It may sound
> like a small matter, but it isn't.
I think you should really try using public/private outline scheme. Just to
remind you of this rather hidden Leo feature.
If an outline has a top level node with the headline
`---begin-private-area---`, then this node is separating the public part of
the outline (before this node) and the private part of the outline (after
this node). The first line of this node should have a path to the public
(shared) Leo document.
Now when you execute c.fileCommands.save_ref() command, the public part is
saved in the shared Leo document. In my private Leo documents I always have
a node with headline `@button n-save @key=Ctrl-s` and the body line always
contains at least these two lines:
c.save()
c.fileCommands.save_ref()
That way my public or reference Leo files never get out of sync.
When I pull changes from the others, I have to remember to execute
`read-ref-file` which updates public part of the outline from the reference
file.
Vitalije
>
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/leo-editor/db3be5ac-30a6-47bf-8d61-fda94cc272b6o%40googlegroups.com.
