The frequently asked-for feature if for clones that don't share children. It's been amusing to think of multi-colored threaded trees, split nodes, and what have you.
The typical use case is to *gather* data from one place to be used in another. For instance, we might want to document a function by special-cloning only its node excluding its children. Imo, this one special case *in no way* justifies changes to Leo's vnodes or positions. Instead, the simplest *and *the most general thing that could possibly work is to gather desired data using a script. 1, The script has complete flexibility to find a desired positions *anywhere*, including other .leo files. This moots the need for cross-file clones. 2. For any gathered position p, the script has complete flexibility to make available p.h, p.b or p.children, depending on the needs of the script. For example, a documentation script might "scrape" one or more .leo files for data, and then create nodes that reference the scraped data. That's all there is to it. 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 https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
