[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[O] Should a human ever set the ID property? Should a human only ever se
From: |
Grant Rettke |
Subject: |
[O] Should a human ever set the ID property? Should a human only ever set the CUSTOM_ID property? |
Date: |
Wed, 17 Aug 2016 23:32:30 -0500 |
Good evening,
Just learned about CUSTOM_ID property. It seems like if you want to
define a custom identifier, then you do it here and that identifier
will get used correctly in all of the weavers. It also seems like a
human should never set the value of the ID property.
The reason I ask is that I've got code that makes sure that every
headline has an ID property set unique because org-uuid makes it so
easy. At the time CUSTOM_ID didn't exist. It kind of looks like I
ought to refactor all of it to use CUSTOM_ID because it will "just
work" in the rest of org mode.
Am I grokking things correctly here?
Sincerely,
Grant Rettke
- [O] Should a human ever set the ID property? Should a human only ever set the CUSTOM_ID property?,
Grant Rettke <=