emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Alexandre Duret-Lutz <adl@lrde.epita.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: diagnosing SRC blocks with different output on export
Date: Fri, 04 Sep 2020 18:12:13 +0200	[thread overview]
Message-ID: <87363xikrm.fsf@gnu.org> (raw)
In-Reply-To: <CA+Xfj9STVHa1s2bnr6KGwVcFTYtAJe9vkTfn4HmWhToAVDF56g@mail.gmail.com> (Alexandre Duret-Lutz's message of "Mon, 27 Jul 2020 14:35:58 +0200")

Hi Alexandre,

Alexandre Duret-Lutz <adl@lrde.epita.fr> writes:

> 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?

Would it be enough to have a new hook called
`org-babel-before-insert-result-hook' that would run before inserting
ressults in `org-babel-insert-result'?

I haven't looked closely, and this requires that the former function
knows what to "replace" before replacing it, but seems feasible.

Also, I'd like to hear from others if they would use such a hook or
if this sounds too overengineered.



      reply	other threads:[~2020-09-04 16:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27 12:35 diagnosing SRC blocks with different output on export Alexandre Duret-Lutz
2020-09-04 16:12 ` Bastien [this message]

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=87363xikrm.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=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).