I find I am constantly confronted with the following problem, and wonder if there is a good way to deal with it.
I seem to need some kind of database query function in Leo, or a dot notation like class variables in Python (so somefunction.somevar will seek out the value of somevar in somefunction, among the many values there). Here is how I imagined it, though I know this won't work in Leo. I start with a branch where data in fields are stored. Entry1 .....<<name>> ..........Paul Example .....<<number>> .........822-4022 I want to clone that branch and use it in different spots elsewhere in my tree. At one node I will have: 1st node .... Where is <<name>>? .........Entry1 clone and at another node: 2nd node ..... What is <<name>>'s number? Is it <<number>>? ..........Entry1 clone Of course, this won't derive properly for two reasons: 1) the named nodes are not directly under the text where the names are used (they are separated by the organizer node "Entry1") and 2) not all the subordinate named nodes are used in the 1st node, so Leo will give an orphan node error. My question: is there any way to get around these two constraints? I.e. 1) allow see-through organizer nodes and 2) allow for orphan nodes to be ignored? The organizer nodes simply make it easier to move data as a block; and it seems like we should be able to override some errors, at least in @nosent derived files. At present I have to cloned each bit of information, which is tedious: 1st node .... Where is <<name>>? .........<<name>> clone 2nd node ..... What is <<name>>'s number? Is it <<number>>? ..........<<name>> clone ..........<<number>> clone --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
