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: Sun, 16 May 2010 11:39:20 +0200	[thread overview]
Message-ID: <F52B6408-C059-4872-9903-BE3BDF7E1ACA@gmail.com> (raw)
In-Reply-To: <87sk5sb43b.wl%dmaus@ictsoc.de>


On May 16, 2010, at 11:14 AM, David Maus wrote:

> Carsten Dominik wrote:
>>>
>>> - `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?
>
> Yes, I'll do that.  Just for the records: using the elisp function as
> fall back for the external program changes the meaning of the
> org-id-method uuidgen: It makes Org use UUIDs for the ID property and
> the external program is the preferred method for doing this.  Hence
> the symbol should better be 'uuid, not 'uuidgen.  So if there is a
> list for backward incompatible changes for a further release (maybe
> 7.x) that are reasonable but not important this should go there.

Yes.

But what I would like to to ask is this:

Make the change and tell people to use `uuid' as the setting.  But if  
a user has set it to uuidgen, be gentle and accept that setting as  
well, treat it like uuid.

Thanks!

- Carsten

  reply	other threads:[~2010-05-16  9:39 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
2010-05-16  9:14       ` David Maus
2010-05-16  9:39         ` Carsten Dominik [this message]
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=F52B6408-C059-4872-9903-BE3BDF7E1ACA@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).