From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [Babel] [Bug] Cache
Date: Mon, 02 Dec 2013 16:46:50 +0100 [thread overview]
Message-ID: <86k3fnw905.fsf@somewhere.org> (raw)
In-Reply-To: 87d2lsihdr.fsf@gmail.com
Hi Eric,
Eric Schulte wrote:
> "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org> 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-i47jiTeKxPI@public.gmane.org>
│ 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.
╰────
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2013-12-02 15:46 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 [this message]
2013-12-06 19:15 ` Eric Schulte
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86k3fnw905.fsf@somewhere.org \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.