From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christophe Schockaert Subject: Re: Properties ID vs. CUSTOM_ID Date: Thu, 22 Dec 2016 20:45:23 +0100 Message-ID: <874m1voii4.fsf@artlab.createcnix.lan> 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> <87mvfoc627.fsf@ericabrahamsen.net> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:47073) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cK9J6-0004zw-Fi for emacs-orgmode@gnu.org; Thu, 22 Dec 2016 14:45:45 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cK9J1-0002pG-BU for emacs-orgmode@gnu.org; Thu, 22 Dec 2016 14:45:40 -0500 Received: from smtp1.tech.numericable.fr ([82.216.111.37]:58130) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cK9J0-0002o1-Ud for emacs-orgmode@gnu.org; Thu, 22 Dec 2016 14:45:35 -0500 Received: from artlab.createcnix.lan (81-64-91-228.rev.numericable.fr [81.64.91.228]) by smtp1.tech.numericable.fr (Postfix) with ESMTP id E801E1462DC for ; Thu, 22 Dec 2016 20:45:32 +0100 (CET) Received: from artlab.createcnix.lan (localhost.createcnix.lan [127.0.0.1]) by artlab.createcnix.lan (Postfix) with ESMTPS id 5E6495EBF1 for ; Thu, 22 Dec 2016 20:45:23 +0100 (CET) In-reply-to: <87mvfoc627.fsf@ericabrahamsen.net> 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 Eric Abrahamsen writes: > Karl Voit writes: > >> 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 I thikn the tricky part would be that we can only ensure ID uniqueness for the current agenda at the time of the ID creation. What if we later merge another set of files where ID were created independantly to our acustomed agenda files ? I like the idea of assigning a date since we would reduce chances to define at the same time the same string and the same day. If meticulous, we could assign a date and a time or random string as you suggest, Eric (a tiny UUID :). I think I read somewhere the first inactive timestamp could be used to tag an entry with a date. At least, I do that frequently. Thus, if available, we could even use it as a date when creating the ID in order to have an indication of the creation time for the heading instead of creation time of the link. Here it is for my suggestions. Dates might not be appropriate for every situation, though... Christophe -- ---------------> mailto:R3vLibre@citadels.eu Once it's perfectly aimed, the flying arrow goes straight to its target. Thus, don't worry when things go right. There will be enough time to worry about if they go wrong. Then, it's time to fire a new arrow towards another direction. Don't sink. Adapt yourself ! The archer has to shoot accurately and quickly. [Words of Erenthar, the bowman ranger] <---------------<<<<