On Fri, Apr 8, 2011 at 3:37 PM, Edward K. Ream <[email protected]> wrote:
> BTW, the g.commands never set p, so at present the whole outline > always gets scanned. Yeah, that's the idea. I had a separate @g.command for partial parsing, but so far it hasn't appeared to be necessary. > My guess is that both pass1 and pass2 should scan up and down the tree > for an @valuespace node, pretty much like the rst3 command does. I don't like this idea. I prefer the scope to be the whole leo document. The valuable data can be everywhere, I don't want it "ghettoed" under some specific subtree. > An alternative is for @button scripts to specify exactly the desired > node, say with g.findNodeAnywhere. Incidentally, g.findNodeAnywhere is something that valuespace is supposed to help you avoid ;-). That is, if a purpose of a node is to be used in a script, just add an @a anchor to it, or change the headline to @= mynode > Whatever we choose, there should be fairly easy ways of dealing with > multiple value spaces. At present, this does not seem straightforward > or even possible. Lesson from ILeo is that it's better to keep things simple, even for a newcomer. I'd like to have just one valuespace for now. -- 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.
