> That depends what you use clones for. If you use them for collecting a > short list of nodes of current interest from a larger tree, you can get > basically the same effect from the bookmarks.py and quickMove.py > plugins. With those plugins enabled, create a node with a headline > containing `@bookmarks`. It doesn't have to be at the start of the > headline. > That's not at all how I use clones. I use them for keeping persistent data persistent and in sync over multiple views and files. For example, in managing a multi-page web site there are numerous text fragments that need to be duplicated across all pages. Cloning these text fragments makes that task so much easier than manually trying to update every instance, or even try to remember where every instance is.
Many of my other document tasks are similar in need for duplicating text fragments and keeping them in sync. Leo is often described as a kind of database, that would be great if I could figure out how to make it be such. That would mean being able to reference the 'master' version of a piece of data and sync to that. Clones sort of do that as long as the reference is 'inside' the same .leo file. How is it possible to reference that data (node) from a different .leo file? Someone mentioned something called a 'UNL'. I can't find any mention of UNLs in the docs glossary. I infer that it is a type of node reference. Where can I get more information about UNLs? Is this a possible answer to my earlier question of referencing a node from a different .leo file? Rob.............. -- 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.
