emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matias Eyzaguirre <matias@fortlogic.net>
To: emacs-orgmode@gnu.org
Subject: Markdown export is non-deterministic?
Date: Fri, 7 Oct 2022 16:31:00 -0600	[thread overview]
Message-ID: <8B2BE812-0A06-4562-9D3F-0515EE4036D1@fortlogic.net> (raw)

I’m using org-mode to generate a markdown README for a project that is
under version control. I’ve noticed that the anchor tags used for the
table of contents seem to be annoyingly random and change from export
to export. Is it possible to make the generated ids deterministic?

For example one invocation of ~org-md-export-to-markdown~ will give me
this:

#+begin_example
1.  [Introduction](#org8f0a2e0)
2.  [Roadmap](#orga3f4ca7)
#+end_example

While exporting a second time, even if there are no changes to the
file, will produce something different such as:

#+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)?

Thanks,
  Matias

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-07 22:31 Matias Eyzaguirre [this message]
2022-10-08 14:57 ` Markdown export is non-deterministic? Max Nikulin
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=8B2BE812-0A06-4562-9D3F-0515EE4036D1@fortlogic.net \
    --to=matias@fortlogic.net \
    --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).