emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Alexandre Duret-Lutz <adl@lrde.epita.fr>
To: emacs-orgmode@gnu.org
Subject: diagnosing SRC blocks with different output on export
Date: Mon, 27 Jul 2020 14:35:58 +0200	[thread overview]
Message-ID: <CA+Xfj9STVHa1s2bnr6KGwVcFTYtAJe9vkTfn4HmWhToAVDF56g@mail.gmail.com> (raw)


Is there a way to mark certain SRC blocks such that if evaluating them
during export produces a result different from the one stored in the
file, then the export process aborts with an error?

I'm using org-mode to document an automaton library, and use org-babel
block to run some examples and have their output automatically
recomputed when the library is improved.  However, some examples
expect some specific automata to be produced, maybe because I discuss
some particularities of that example automaton in the text ; if an
update of the library causes this to change, I need to detect that
change to adjust all the text around it in the documentation, or find
a better exemple.   So I'd like org-mode to signal me that my expected
result is non-longuer what is produced by causing the export (and
therefore my build) to fail.

Can this be achieved already?

Reading https://orgmode.org/manual/Results-of-Evaluation.html it seems
like I'd like I'm asking for a new form of handling.  Something like
"compare" instead of "replace".

Best regards
Alexandre Duret-Lutz

             reply	other threads:[~2020-07-27 12:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27 12:35 Alexandre Duret-Lutz [this message]
2020-09-04 16:12 ` diagnosing SRC blocks with different output on export 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=CA+Xfj9STVHa1s2bnr6KGwVcFTYtAJe9vkTfn4HmWhToAVDF56g@mail.gmail.com \
    --to=adl@lrde.epita.fr \
    --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).