emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Max Nikulin <manikulin@gmail.com>
To: Matias Eyzaguirre <matias@fortlogic.net>, emacs-orgmode@gnu.org
Subject: Re: Markdown export is non-deterministic?
Date: Sat, 8 Oct 2022 21:57:21 +0700	[thread overview]
Message-ID: <4b4b8e19-e05a-1da3-cda1-d4698113f72a@gmail.com> (raw)
In-Reply-To: <8B2BE812-0A06-4562-9D3F-0515EE4036D1@fortlogic.net>

On 08/10/2022 05:31, Matias Eyzaguirre wrote:
> 
> #+begin_example
> 1.  [Introduction](#org775f005)
> 2.  [Roadmap](#orgccee397)
> #+end_example
> 
> While these identifiers are generally not visible to a reader, they
> add noise to the version control diffs. I'm wondering if it's possible
> to force the relevantrandom number generator to use a fixed seed or,
> more ideally, have the ids be based on the section title (or its
> hash)?

You may try to add CUSTOM_ID property to section. Current behavior is 
intentional, see e.g.

Nicolas Goaziou… Re: HTML export uses anchor ids which change on every 
export. Sat, 29 May 2021 21:50:24 +0200. 
https://list.orgmode.org/87bl8tz5dr.fsf@nicolasgoaziou.fr

A long discussion:

Samuel Wales. stability of toc links. Tue, 8 Dec 2020 16:28:46 -0700. 
https://list.orgmode.org/CAJcAo8tXVW39h18FUXLtwoDYNKQsFHqCp+YDiyWfLee29B1PRw@mail.gmail.com

Some people managed to implement anchors based on heading titles

TEC. [Interest] Determanistic Org IDs. Sun, 19 Jul 2020 22:27:31 +0800. 
https://list.orgmode.org/E1jxAjg-0004Dk-U6@lists.gnu.org


  reply	other threads:[~2022-10-08 14:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-07 22:31 Markdown export is non-deterministic? Matias Eyzaguirre
2022-10-08 14:57 ` Max Nikulin [this message]
2022-10-09  3:50 ` Ihor Radchenko
2022-10-16  9:24 ` Dominique Dumont
2022-10-16  9:44   ` Ihor Radchenko

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=4b4b8e19-e05a-1da3-cda1-d4698113f72a@gmail.com \
    --to=manikulin@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=matias@fortlogic.net \
    /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).