From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: Properties ID vs. CUSTOM_ID
Date: Thu, 22 Dec 2016 13:40:05 -0800 [thread overview]
Message-ID: <87a8bnzlqi.fsf@ericabrahamsen.net> (raw)
In-Reply-To: CADn3Z2Kj4PByi0VRtOSB0w4Zj=2dZc7XYniXPKAZi4B5QAUMvw@mail.gmail.com
Carsten Dominik <dominik@uva.nl> writes:
> Dear all,
>
> before continuing this discussion, and before reinventing, you might
> want to take a look at how org-id.el currently does create unique IDs.
> In particular, take a look at these variables:
>
> org-id-prefix
> org-id-method
> org-id-include-domain
>
> In particular, the docstring of the variable org-id-method is
>
> "The method that should be used to create new IDs.
>
> An ID will consist of the optional prefix specified in
> `org-id-prefix',
> and a unique part created by the method this variable specifies.
>
> Allowed values are:
>
> org Org's own internal method, using an encoding of the current
> time to
> microsecond accuracy, and optionally the current domain of
> the
> computer. See the variable `org-id-include-domain'.
>
> uuid Create random (version 4) UUIDs. If the program defined in
> `org-id-uuid-program' is available it is used to create the
> ID.
> Otherwise an internal functions is used."
>
> Hope this helps.
Right, and we're not trying to reinvent any wheels, just get a
user-readable string in there while still retaining uniqueness. Ie, it
would probably be enough if org-id-prefix could be set to 'entry, and
org then generated a prefix by munging the entry text:
* My Great Header
:PROPERITIES:
:ID: my-great-header-44d1-b804-d11657131237
:END:
next prev parent reply other threads:[~2016-12-22 21:40 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
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 [this message]
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=87a8bnzlqi.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).