On Fri, 18 Nov 2011 05:22:57 -0800 (PST) Josef <[email protected]> wrote:
> not only would I vote for this, but in addition, the generated path > should be *relative* to the path in the @path directive, not absolute. > E.g. use os.path.relpath(path[, start]) where start is the path > specified by the (cascaded) @path directive. In what context would this relative path exist - oh, I get it, p.nodePath() or whatever it's called would return a relative path. Relative to the most recent absolute path ancestor, or the current location of the .leo file, if there are no absolute path ancestors. That could be useful although I suspect the most common use case of p.nodePath() is to feed it into open(), so perhaps p.nodePath() should return an absolute path and p.nodePath(relative=True) should return a relative path. Cheers -Terry -- 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.
