Karl Voit <devn...@karl-voit.at> writes: > * John Kitchin <jkitc...@andrew.cmu.edu> wrote: >> >> There is not an issue using a human-readable id in :ID: as long as it is >> unique. It will store fine, link fine, etc... > > I also think so because I am only using human-readable :ID: without > any issue so far. > > However, the argument was that no human should set :ID: but use > :CUSTOM_ID: *instead*. See also the old thread I linked before. > > I'd prefer using manually written :ID: instead since migration would > not be trivial to me.
You could also use the `org-property-set-functions-alist' trick with the :ID: property. If you added an "ID" entry to that alist, Org's usual automatic id creation would be unaffected, but if you set ID manually, you could write a function that would first prompt for your human-readable string, then check for ID uniqueness and append random characters to your string until it was unique. I think that would be a nice addition to org-id.el. Eric
