From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eric Abrahamsen Subject: Re: Properties ID vs. CUSTOM_ID Date: Thu, 22 Dec 2016 07:54:56 -0800 Message-ID: <87mvfoc627.fsf@ericabrahamsen.net> References: <2016-08-25T14-36-57@devnull.Karl-Voit.at> <877fb429j4.fsf@saiph.selenimh> <2016-08-25T17-05-15@devnull.Karl-Voit.at> <87mvg2t8g0.fsf@artlab.createcnix.lan> <2016-12-12T12-38-45@devnull.Karl-Voit.at> <2016-12-12T15-59-38@devnull.Karl-Voit.at> <2016-12-18T13-12-13@devnull.Karl-Voit.at> <2016-12-20T20-43-27@devnull.Karl-Voit.at> <2016-12-22T11-00-17@devnull.Karl-Voit.at> <2016-12-22T16-27-34@devnull.Karl-Voit.at> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43996) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cK5i8-0003D0-TM for emacs-orgmode@gnu.org; Thu, 22 Dec 2016 10:55:17 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cK5i5-0002GX-Rc for emacs-orgmode@gnu.org; Thu, 22 Dec 2016 10:55:17 -0500 Received: from [195.159.176.226] (port=42521 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cK5i5-0002El-MP for emacs-orgmode@gnu.org; Thu, 22 Dec 2016 10:55:13 -0500 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1cK5ht-0008Fk-NY for emacs-orgmode@gnu.org; Thu, 22 Dec 2016 16:55:01 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org Karl Voit writes: > * John Kitchin 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