From: Karl Voit <devnull@Karl-Voit.at>
To: emacs-orgmode@gnu.org
Subject: Properties ID vs. CUSTOM_ID (was: Automatically Generating IDs From Title and Date)
Date: Tue, 20 Dec 2016 20:57:27 +0100 [thread overview]
Message-ID: <2016-12-20T20-43-27@devnull.Karl-Voit.at> (raw)
In-Reply-To: CAJcAo8uQD-ub7+R1y8Km_=Td33x-NDSKT6neqnKtE1pfqQuk9Q@mail.gmail.com
* Samuel Wales <samologist@gmail.com> wrote:
> On 12/18/16, Karl Voit <devnull@karl-voit.at> wrote:
>> Usually, my IDs start with the current ISO day to enforce uniqueness
>> and look like this:
>
> my understanding, which might be incorrect, is that custom id is for
> human-readable purposes, while id is for uuid. although you could
> prepend to uuid.
There once was a discussion on this topic here:
https://lists.gnu.org/archive/html/emacs-orgmode/2016-08/msg00165.html
I am a bit worried: So far, I got 125870 manually set ID properties
in my Org-mode files.
To me, using :ID: was straight forward since I never read about any
other ID when I began with Org-mode in 2011.
Many features required me to have an :ID: and no feature I stumbled
upon required me to have something else as reference:
id:this-is-an-id, making references using org-store-link, and so
forth.
So let's search through the manual:
http://orgmode.org/org.html#Internal-links
http://orgmode.org/org.html#Handling-links
http://orgmode.org/org.html#Search-options
Well, either this did not exist in 2011 or I was not paying
attention. I never faced any disadvantage, using ID properties
instead.
Do I really need to migrate and risk broken links? Or is there a
safe way to move to CUSTOM_ID?
Are there advantages when I switch to CUSTOM_IDs?
Do I really have to have a CUSTOM_ID *and* an ID set for being able
to reference any heading via human-readable ids *and* features like
org-store-link and so on?
--
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
> get Memacs from https://github.com/novoid/Memacs <
https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github
next prev parent reply other threads:[~2016-12-20 19:57 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 ` Karl Voit [this message]
2016-12-22 10:03 ` Properties ID vs. CUSTOM_ID (was: Automatically Generating IDs From Title and Date) 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
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=2016-12-20T20-43-27@devnull.Karl-Voit.at \
--to=devnull@karl-voit.at \
--cc=emacs-orgmode@gnu.org \
--cc=news1142@Karl-Voit.at \
/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).