emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: TEC <tecosaur@gmail.com>
To: Alexander Adolf <alexander.adolf@condition-alpha.com>
Cc: org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: [Interest] Determanistic Org IDs
Date: Fri, 24 Jul 2020 22:53:46 +0800	[thread overview]
Message-ID: <87o8o5m04k.fsf@gmail.com> (raw)
In-Reply-To: <eb7766e8cf6d4e1d635b81b8b9242b72@condition-alpha.com>

Alexander Adolf <alexander.adolf@condition-alpha.com> writes: 
> Hello Timothy, 

Hi :)
> Interesting. Just a thought: have you considered computing a 
> SHA-2 hash... 
I have not. Simply put, I fail to see any advantage.
> This would have the advantage of solving both, your "noise 
> issue" and at the same time removing the threat of id 
> collisions; but at the cost of not having "speaking" links. 

As it stands there is no issue with ID collisions within the same 
file, just in-case you wanted to look across files.

This is ensured in the (while (--any (equal ref (car it)) cache) 
... block.

All the best,


  reply	other threads:[~2020-07-24 14:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1jxAju-0004Dk-3O@lists.gnu.org>
2020-07-24 12:09 ` [Interest] Determanistic Org IDs Alexander Adolf
2020-07-24 14:53   ` TEC [this message]
     [not found] <E1jxAkG-00052l-OS@lists.gnu.org>
2020-07-20  3:45 ` TEC
2020-07-19 14:27 TEC

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=87o8o5m04k.fsf@gmail.com \
    --to=tecosaur@gmail.com \
    --cc=alexander.adolf@condition-alpha.com \
    --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).