On Tue, Jul 8, 2014 at 10:11 AM, Jacob Peck <[email protected]> wrote:
> I'm not well versed in the gnx. I know it's unique per node, but not much > else. The gnx is both unique and immutable. It is the permanent, *unchanging* identity of a node. You can't change this behaviour without breaking clones. Each gnx has the form <user>.<time>.<number> for example: ekr.20140707060759.17644 The .<number> field exists only if several nodes would otherwise have the same gnx. gnx's are, iirc, created if necessary when Leo writes a node for the first time. > Is it updated every time the node is updated? No. A gnx has nothing to do with content. It has everything to do with identity. > can this behavior be broken without killing Leo's core? Nope. If you want a content-related key, try using the sha-1 hash :-) Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
