ja fro <[email protected]> writes: > I have checked the function ` org-id-update-id-locations` which > collects IDs and populate `.orgids` database and it seems to me it > ignores the one-line definition of ID. It looks only for `:ID:` regexp > I think (if it is false alarm I am sorry I am still elisp beginner). > ``` > (id-regexp > (rx (seq bol (0+ (any "\t ")) ":ID:" (1+ " ") (not (any " "))))) > (seen-ids (make-hash-table :test #'equal))
Yes, you are right. `org-id-update-id-locations' only considers actual ID properties, not generic default property setting. This is the same in other places (e.g. `org-id-find-id-in-file'). Also, it feels awkward to use the global default ID as reference. Because it is "default", it will be an ID for all the headings without ID explicitly set, making such ID non-unique, which goes against the idea of id: link design. I think that your use case should not be supported because of this ambiguity. Thus, I do not think that current behavior of Org mode needs to be changed. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
