On Mon, 26 Dec 2011 19:27:58 -0800 (PST) HansBKK <[email protected]> wrote:
> What about the "Set node to absolute path recursive" issue I outlined? To > my mind, if you enable batch conversion to absolute @paths, there should be > either an automated way back to relative ones (preferred), or at least a > visual indicator of which ones need to be fixed manually out in the > filesystem. Right now I'm using external regex search-and-replace tools to > find the abspaths hidden in the shadow files, which is fine but definitely > a kludge 8-) I suspect "Set node to absolute path recursive" came in to being because I was making recursive versions of all the commands - to be honest I don't see why you'd want to do it. A single "Set node to absolute path" is obviously useful for breaking off a part of the tree and moving it. Perhaps you're using the recursive version to prep the whole tree for easy dismantling? Anyway, I've made a note to look at the inconsistency and configurability issues you noted. > The "master" > tree structure carries no meaning, its only purpose is to have an > unchanging location to link UNLs to Ok, that makes sense :) 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.
