From: Karl Voit <devnull@Karl-Voit.at>
To: emacs-orgmode@gnu.org
Subject: Re: Properties ID vs. CUSTOM_ID
Date: Thu, 22 Dec 2016 16:30:46 +0100 [thread overview]
Message-ID: <2016-12-22T16-27-34@devnull.Karl-Voit.at> (raw)
In-Reply-To: CAJ51ETrmtRtk_6TN-dDg16D3F43jmvD=JFz9Z7ijYb-+vhhX+g@mail.gmail.com
* 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.
I'd prefer using manually written :ID: instead since migration would
not be trivial to me.
--
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-22 15:31 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 ` Karl Voit [this message]
2016-12-22 15:40 ` Properties ID vs. CUSTOM_ID 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-22T16-27-34@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).