On Thu, Dec 26, 2013 at 6:19 AM, Edward K. Ream <[email protected]> wrote:
> But bookmarks give you the same advantages, with even more complete >> >> context for the nodes you're editing, you see the node in its full >> >> normal context, so you see siblings and parents as well, which may be >> >> useful. >> > > This extra context is precisely what I *don't* want. It had better be > the case, generally, that the context of the node *doesn't* matter. If it > does, Leo's design is broken. > > I muddied the water unnecessarily here. The design of Leo has nothing to do with this discussion. It would have been clearer if I had said that with clones I can choose *however much* context seems right for me. Sometimes, in fact, I clone an entire @file node. This gives me a chance to point out something truly great about bookmarks and clones: they are both completely "weightless". A bookmark costs (almost) nothing, regardless of the size of the tree to which it refers. The same is also true of clones! Internally, a clone is just a pointer (reference) to an already-existing vnode. In .leo files, a clone is simply another <v> xml element. <v> elements refer to <t> elements that contain the body text, so again there is essentially no cost to adding a clone. Edward -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
