emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: David Masterson <dsmasterson@outlook.com>
To: Nathan Neff <nathan.neff@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: CUSTOM_ID vs ID
Date: Fri, 2 Aug 2019 04:54:55 +0000	[thread overview]
Message-ID: <BYAPR07MB5734F8BC58384586651105A5A5D90@BYAPR07MB5734.namprd07.prod.outlook.com> (raw)
In-Reply-To: <87r269tkfk.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Mon, 29 Jul 2019 08:38:07 +0200")

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> David Masterson <dsmasterson@outlook.com> writes:
>
>> Can you talk a little bit about how IDs are generated so that they are
>> absolutely unique?
>
> See `org-id-new'. By default, it uses "uuidgen" command.
>
>> IDs sound like something that would be useful for synchronizing
>> information between two (or more) separate Org systems - the ID could be
>> updated whenever a change occurs and then used to determine what needs
>> synchronization.  True?
>
> I think this is different. ID property is meant to never change once
> created. If you update it, you lose the reference to the headline, which
> defeats the intended purpose.

Ah. Gotcha.
--
David

  reply	other threads:[~2019-08-02  4:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-27 23:35 CUSTOM_ID vs ID Nathan Neff
2019-07-28  8:10 ` Nicolas Goaziou
2019-07-29  4:23   ` David Masterson
2019-07-29  6:38     ` Nicolas Goaziou
2019-08-02  4:54       ` David Masterson [this message]
2019-07-30  0:38   ` Nathan Neff
2019-08-01  7:55     ` Richard Lawrence
2019-08-09 11:13     ` Adam Porter
2019-08-02 14:53   ` Nathan Neff
2019-08-09 11:12     ` Adam Porter
2019-08-18  0:53   ` Jorge P. de Morais Neto
2019-08-18 10:40     ` Nicolas Goaziou
2019-08-18 14:24       ` Jorge P. de Morais Neto
2019-08-18 15:05         ` Nicolas Goaziou

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=BYAPR07MB5734F8BC58384586651105A5A5D90@BYAPR07MB5734.namprd07.prod.outlook.com \
    --to=dsmasterson@outlook.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=nathan.neff@gmail.com \
    /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).