emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: TRS-80 <trs-80@isnotmyreal.name>
To: emacs-orgmode@gnu.org
Subject: Re: Any reason not to generate my own custom ID value (NOT CUSTOM_ID)?
Date: Thu, 10 Sep 2020 18:16:30 -0400	[thread overview]
Message-ID: <bd17f96ca54603ab3539c489a66d97a6@isnotmyreal.name> (raw)
In-Reply-To: <HE1PR0202MB2857EAD656FC70EDDB12E10DDA270@HE1PR0202MB2857.eurprd02.prod.outlook.com>

On 2020-09-10 18:00, Gustav Wikström wrote:
> Hi TRS-80,
>  Your approach should work just fine. So fine, in fact, that it's
> already kind of built in! Configure org-id-method and set it to 'ts
> and you'll get timestamps as ID instead of uuid.
>  I do believe the manual lacks a description for this. Not entirely
> sure though, and can't check atm. But the configuration is there none
> the less, and supported.
>  Kind regards
>  Gustav

Hi Gustav,

Thanks for the fast reply.

I am aware of the 'ts' option to org-id-method which does not seem to
be documented in manual, only docstring of its defcustom in org-id.el.
I had left that detail out for the sake of brevity.  :)

My problem with that is that I do not like the format it outputs which
is "%Y%m%dT%H%M%S.%6N" (in other words, output which looks like
"20200910T180910.747026").  Only a little bit better than the "uuid"
option, IMHO!  :)

It would be great if that format-time-string was a configurable
variable, instead of hard coded, but alas it is not.  Well, since we
are now on that subject, perhaps I should ask is there some reason for
this?  Or would Bastien perhaps consider something like that?  :)))


  reply	other threads:[~2020-09-10 22:17 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-10 20:02 Any reason not to generate my own custom ID value (NOT CUSTOM_ID)? TRS-80
2020-09-10 22:00 ` Gustav Wikström
2020-09-10 22:16   ` TRS-80 [this message]
2020-09-13 20:18     ` Bastien
2020-09-10 22:20 ` Samuel Wales
2020-09-10 23:33   ` TRS-80
2020-09-11  1:06     ` Ihor Radchenko
2020-09-11  1:31       ` TRS-80
2020-09-11  7:51         ` Ihor Radchenko
2020-09-13 20:19           ` Bastien
2020-09-23  7:19           ` Bastien
2020-09-23  7:43             ` [PATCH] " Ihor Radchenko
2020-09-23  7:48               ` Bastien
2020-09-23  8:08                 ` Ihor Radchenko
2020-09-23  8:30                   ` Bastien
2020-09-23  8:40                 ` Ihor Radchenko
2020-09-23  8:48                   ` Bastien
2021-04-25 14:19                   ` Bastien

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:

  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=bd17f96ca54603ab3539c489a66d97a6@isnotmyreal.name \
    --to=trs-80@isnotmyreal.name \
    --cc=emacs-orgmode@gnu.org \


* 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


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).