From mboxrd@z Thu Jan  1 00:00:00 1970
From: Grant Rettke <gcr@wisdomandwonder.com>
Subject: 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
Message-ID: <CAAjq1mdhcEpQFxwsg7DrTcT+uqnwHhL1=Y7H3pVvLc_DKoHhhw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:58348)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <grettke@gmail.com>) id 1baF0L-0007v0-7L
	for emacs-orgmode@gnu.org; Thu, 18 Aug 2016 00:32:37 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <grettke@gmail.com>) id 1baF0J-0005o1-Dv
	for emacs-orgmode@gnu.org; Thu, 18 Aug 2016 00:32:32 -0400
Received: from mail-it0-x22a.google.com ([2607:f8b0:4001:c0b::22a]:35016)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <grettke@gmail.com>) id 1baF0J-0005nr-90
	for emacs-orgmode@gnu.org; Thu, 18 Aug 2016 00:32:31 -0400
Received: by mail-it0-x22a.google.com with SMTP id x131so17548641ite.0
	for <emacs-orgmode@gnu.org>; Wed, 17 Aug 2016 21:32:30 -0700 (PDT)
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode/>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: "Emacs-orgmode"
	<emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>

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