emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christophe Schockaert <R3vLibre@citadels.eu>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Properties ID vs. CUSTOM_ID
Date: Thu, 22 Dec 2016 20:23:53 +0100	[thread overview]
Message-ID: <8760mbojhy.fsf@artlab.createcnix.lan> (raw)
In-Reply-To: <CAJ51ETrrOUjOT4M6XnyG3RAZP__mzFsrHWEYWMsqLRgip7wyJA@mail.gmail.com>


John Kitchin writes:
> On Thu, Dec 22, 2016 at 10:30 AM, Karl Voit <devnull@karl-voit.at> wrote:
>
>> * John Kitchin <jkitchin@andrew.cmu.edu> 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.
>>
> That is just be a convention though, and as long as the IDs are unique, it
> does not matter who sets them.
>
> John
That's how I ended up understanding their use.

When I read the manual (http://orgmode.org/manual/Handling-links.html),
it's actually possible to define both IDs for the same entry:

:  So using this command (added: org-store-link) in Org buffers will
:  potentially create two links: a human-readable from the custom ID, and
:  one that is globally unique and works even if the entry is moved from
:  file to file. Later, when inserting the link, you need to decide which
:  one to use.

Indeed, if both IDs are available, when inserting the link, we can
choose which ID will be used as target.

Also, we should note that the scope for CUSTOM_ID is the current file
only. That's what prevented me to migrate human readable IDs to
CUSTOM_IDs, and led me to consider the choice between the two as a
convention.

And I guess, that you would need ID available between different files
too, Karl, as you expect org-depend to be usable accross different files
:o)

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] <---------------<<<<

  reply	other threads:[~2016-12-22 19:24 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-25 12:43 org-depend: dependencies between TODO entries in different files Karl Voit
2016-08-25 14:44 ` Nicolas Goaziou
2016-08-25 15:11   ` Karl Voit
2016-12-08  6:44     ` Carsten Dominik
2016-12-08 10:16       ` Jorge Morais Neto
2016-12-08 11:11         ` Samuel Loury
2016-12-12 10:21         ` Jorge Morais Neto
2016-12-08 14:37       ` Nicolas Goaziou
2016-12-11 22:19       ` Christophe Schockaert
2016-12-12 11:57         ` Karl Voit
2016-12-12 13:57           ` Carsten Dominik
2016-12-12 15:17             ` Karl Voit
2016-12-12 22:23               ` Christophe Schockaert
2016-12-18 12:12               ` org-depend improvements: ID picker Karl Voit
2016-12-18 17:49                 ` Eric Abrahamsen
2016-12-20 20:01                   ` a general " Karl Voit
2016-12-20 21:21                     ` Eric Abrahamsen
2016-12-18 12:14               ` Automatically Generating IDs From Title and Date Karl Voit
2016-12-18 19:36                 ` Samuel Wales
2016-12-20 19:57                   ` Properties ID vs. CUSTOM_ID (was: Automatically Generating IDs From Title and Date) Karl Voit
2016-12-22 10:03                     ` Karl Voit
2016-12-22 14:29                       ` John Kitchin
2016-12-22 15:30                         ` Properties ID vs. CUSTOM_ID Karl Voit
2016-12-22 15:40                           ` John Kitchin
2016-12-22 19:23                             ` Christophe Schockaert [this message]
2016-12-22 15:54                           ` Eric Abrahamsen
2016-12-22 19:45                             ` Christophe Schockaert
2016-12-22 21:02                               ` Eric Abrahamsen
2016-12-22 21:31                                 ` Carsten Dominik
2016-12-22 21:39                                   ` Carsten Dominik
2016-12-22 21:40                                   ` Eric Abrahamsen
2016-12-22 22:19                                     ` Christophe Schockaert
2016-12-22 17:10                           ` Samuel Wales
2016-12-22 17:13                             ` Samuel Wales
2016-12-18 12:17               ` org-depend improvements: TRIGGER in Combination With Set SCHEDULED Karl Voit
2016-12-18 12:18               ` org-depend improvements: Canceled Tasks Do Cancel Their Dependencies as Well Karl Voit
2016-12-12 19:25             ` org-depend: dependencies between TODO entries in different files Samuel Wales
2016-12-12 21:13               ` Karl Voit
2016-12-18 19:27                 ` Samuel Wales

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8760mbojhy.fsf@artlab.createcnix.lan \
    --to=r3vlibre@citadels.eu \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).