emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: David Maus <dmaus@ictsoc.de>
Cc: org-mode <emacs-orgmode@gnu.org>
Subject: Re: [patch] org-id: New org-id-method 'uuid' w/ elisp function that creates random uuid
Date: Sat, 15 May 2010 09:02:35 +0200	[thread overview]
Message-ID: <8B270AAC-10B3-40A8-B7C9-682308DEBD6F@gmail.com> (raw)
In-Reply-To: <87aasa7a6e.wl%dmaus@ictsoc.de>


On May 8, 2010, at 4:14 PM, David Maus wrote:

> Carsten Dominik wrote:
>> what is the difference/advantage of this idea over using uuidgen as
>> Org does now?
>
> Well, it allows uuids without depending on the presence of the uuidgen
> binary.  E.g. I happen to occasionally use computers I have no control
> of and carry my Emacs/Org configuration with me.
>
> Without the elisp function the ID properties of my headlines are in an
> inconsistent format depending on whether uuidgen was present on the
> machine I created the ID property or not.
>
> It may be a little pedantic but I'd like to be specific in what format
> the IDs have and like the idea of having IDs that follow an
> established standard.
>
> Maybe another usage of the function could be:
>
> - org-id-method can be 'org for Org's id mechanism or 'uuid for uuids

I think it should be either uuidgen (for backward compatibility) or  
uuid.

>
> - `org-id-new' uses uuidgen if present and falls back to the elisp
>   function otherwise

I like that.  WOuld you like to modify your patch accordingly?

- Carsten

  reply	other threads:[~2010-05-15  7:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-07 15:57 [patch] org-id: New org-id-method 'uuid' w/ elisp function that creates random uuid David Maus
2010-05-08  5:03 ` Carsten Dominik
2010-05-08 14:14   ` David Maus
2010-05-15  7:02     ` Carsten Dominik [this message]
2010-05-16  9:14       ` David Maus
2010-05-16  9:39         ` Carsten Dominik
2010-05-16 14:16           ` David Maus

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=8B270AAC-10B3-40A8-B7C9-682308DEBD6F@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=dmaus@ictsoc.de \
    --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).