From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
Subject: Re: [Babel] [Bug] Cache
Date: Mon, 02 Dec 2013 16:46:50 +0100
Message-ID: <86k3fnw905.fsf@somewhere.org>
References: <86fvqqc8jb.fsf@somewhere.org> <87d2lsihdr.fsf@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request-mXXj517/zsQ@public.gmane.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode>
List-Post: <mailto:emacs-orgmode-mXXj517/zsQ@public.gmane.org>
List-Help: <mailto:emacs-orgmode-request-mXXj517/zsQ@public.gmane.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request-mXXj517/zsQ@public.gmane.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org-mXXj517/zsQ@public.gmane.org
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org

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 b=
een
>> 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 N=
oWeb
>> 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 t=
he
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:

  =E2=95=AD=E2=94=80=E2=94=80=E2=94=80=E2=94=80
  =E2=94=82 From: Achim Gratz <Stromeko-i47jiTeKxPI@public.gmane.org>
  =E2=94=82 Subject: Re: [PATCH] * lisp/ob-core.el (org-babel-execute-src-b=
lock):
  =E2=94=82 	insert hash for silent results
  =E2=94=82 Date: Sun, 10 Mar 2013 09:52:10 +0100 (38 weeks, 1 day, 6 hours=
 ago)
  =E2=94=82
  =E2=94=82 [...]
  =E2=94=82
  =E2=94=82 But back to my earlier remark about the hash value actually bei=
ng a
  =E2=94=82 signature of the source block and not the result.  If I use now=
eb
  =E2=94=82 references, the reference text is cached, not its expansion.
  =E2=95=B0=E2=94=80=E2=94=80=E2=94=80=E2=94=80

Best regards,
  Seb

--=20
Sebastien Vauban