emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alexander Adolf <alexander.adolf@condition-alpha.com>
To: TEC <tecosaur@gmail.com>, org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: [Interest] Determanistic Org IDs
Date: Fri, 24 Jul 2020 14:09:13 +0200	[thread overview]
Message-ID: <eb7766e8cf6d4e1d635b81b8b9242b72@condition-alpha.com> (raw)
In-Reply-To: <E1jxAju-0004Dk-3O@lists.gnu.org>

Hello Timothy,

TEC <tecosaur@gmail.com> writes:

> [...]
> Pros:
>  - Reduced 'noise' if exported files are commited - (With HTML) 
>  links to particular elements in a file keep working across 
>    multiple versions, most of the time 
>  - (With HTML) links become more descriptive 
> Cons:
> - Inceased chance of ID collisions across files Longer IDs  I 
> - think this could make a nice option for export settings. I'm 
> - aware of the 9.5 feature freeze, but thought I'd mention the 
> - idea to see if there's any interest in it.
> If you want to see what I've got happening, see 
> https://tecosaur.github.io/emacs-config/config.html#nicer-generated-heading.
> [...]

Interesting. Just a thought: have you considered computing a SHA-2 hash
over either the totality of the heading and all its children (if you
want the links to change when the content changes), or only the heading
itself (keeping the id invariant for as long as the heading remains
unchanged, but content below it can change)?

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.

Hoping to have helped,


       reply	other threads:[~2020-07-24 12:09 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 ` Alexander Adolf [this message]
2020-07-24 14:53   ` [Interest] Determanistic Org IDs TEC
     [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=eb7766e8cf6d4e1d635b81b8b9242b72@condition-alpha.com \
    --to=alexander.adolf@condition-alpha.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tecosaur@gmail.com \


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