emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <schulte.eric@gmail.com>
To: Sebastien Vauban <sva-news@mygooglest.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [Babel] [Bug] Cache
Date: Fri, 06 Dec 2013 12:15:14 -0700	[thread overview]
Message-ID: <87d2l96b2y.fsf@gmail.com> (raw)
In-Reply-To: 86k3fnw905.fsf@somewhere.org

"Sebastien Vauban" <sva-news@mygooglest.com> writes:

> Hi Eric,
> Eric Schulte wrote:
>> "Sebastien Vauban" <sva-news@mygooglest.com> writes:
>>> IIRC, some time ago, a bug involving the computation of the hash (when
>>> option cache is enabled) and NoWeb code blocks. I remember that it had been
>>> fixed.
>>> However, the following example shows it's not (true anymore):
>>> --8<---------------cut here---------------start------------->8---
>>> #+PROPERTY: cache yes
>>> #+name: common-code
>>> #+begin_src R :eval no
>>> s <- "Hello"
>>> #+end_src
>>> #+begin_src R :noweb yes
>>> <<common-code>>
>>> print(s)
>>> #+end_src
>>> #+results[f472c44e64e310a6d06544dbdfba558a709873a7]:
>>> : Hello
>>> --8<---------------cut here---------------end--------------->8---
>>> Change the "common code" block: edit "Hello", for example, and you'll see
>>> that the evaluation of the other code block is not redone (like if the NoWeb
>>> code was not expanded for computing the hash). It stays printing "Hello".
>> Could you git bisect this breakage to isolate the offending commit?
> I couldn't find any version where my ECM would work. Though, I was sure to have
> read comments about that problem -- I never used that situation myself in the
> past, so I just assumed it had been fixed in the meanwhile. It seems not.
> And here the post of Achim where he explains that problem:
>   ╭────
>   │ From: Achim Gratz <Stromeko@nexgo.de>
>   │ Subject: Re: [PATCH] * lisp/ob-core.el (org-babel-execute-src-block):
>   │ 	insert hash for silent results
>   │ Date: Sun, 10 Mar 2013 09:52:10 +0100 (38 weeks, 1 day, 6 hours ago)
>   │
>   │ [...]
>   │
>   │ But back to my earlier remark about the hash value actually being a
>   │ signature of the source block and not the result.  If I use noweb
>   │ references, the reference text is cached, not its expansion.
>   ╰────

In that thread we agreed that the expansion of no-web references
*should* be included in code blocks for hashing, but no-one has had the
time to implement this.

I believe this is still the case.

Eric Schulte
PGP: 0x614CA05D

  reply	other threads:[~2013-12-06 19:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-21 11:13 [Babel] [Bug] Cache Sebastien Vauban
2013-11-22 15:03 ` Eric Schulte
2013-12-02 15:46   ` Sebastien Vauban
2013-12-06 19:15     ` Eric Schulte [this message]
2013-12-06 19:57       ` Achim Gratz
2013-12-06 20:04         ` Sebastien Vauban
2013-12-07  2:29         ` Eric Schulte

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=87d2l96b2y.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=sva-news@mygooglest.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).