As of rev 5584, Leo will write cloned nodes anywhere in @file trees. This
has been a frequently requested feature and fixes several related bugs. For
example::
+ @file test.py
+ cloned_node
+ cloned_node
Assuming the @file node contains an @others directive, both copies of the
cloned node will be written to the test.py, and properly read when Leo next
loads the external file.
I have been the logic for several days without any difficulties, but this
is still an experimental feature. Please report any problems immediately.
Edward
P.S. Clones are still strictly prohibited from descending from themselves,
but this has no effect on the read/write logic--Leo enforces this
constraint whenever you try to move a clone so that it would be a
descendant of itself.
EKR
--
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].
Visit this group at http://groups.google.com/group/leo-editor?hl=en.
For more options, visit https://groups.google.com/groups/opt_out.