Thanks for responding! I wasn't actually interested in the creation data as data, it's just a means to assign an arbitrary value that isn't going to change - the headline string is just a temporary placeholder, possibly to be pasted within the body if it's relevant.
Re your implementation - are you referring to using what I call Leo's "internal meta" data structures (p/t/v whatever, all greek to me) ? It's true the cloning mechanism is also based on "internal meta" - ideally I'd prefer something actually stored (ideally discreetly) in my plaintext content, but at least the clone mechanism is clearly visible and open to manipulation in Leo's UI without programming; I don't know from python. I've seen reference to a type of "tagging" using those internal meta data, but have no idea how to implement that. I do plan to investigate other tagging implementations, particularly in finding a migration path for my 20K+ bookmarks currently hostage to the vagaries of del.icio.us - I believe the most "mainstream" method at this point uses the quickmove plugin? And I'm assuming that also uses cloning. . . Finally, in this case my primary objective is to ensure tree-path stability for UNLs - does your proposal accomplish that? -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To view this discussion on the web visit https://groups.google.com/d/msg/leo-editor/-/IM8UJ1qfNBgJ. 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.
