emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Eric Schulte" <schulte.eric@gmail.com>
To: Andreas Leha <andreas.leha@med.uni-goettingen.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: [babel] Bug? :cache yes ignored when :noweb yes
Date: Sun, 27 Feb 2011 11:03:52 -0700	[thread overview]
Message-ID: <87tyfp9wxj.fsf@gmail.com> (raw)
In-Reply-To: <4D68DB0B.6050704@med.uni-goettingen.de> (Andreas Leha's message of "Sat, 26 Feb 2011 11:50:51 +0100")

Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:

> Hi Eric,
>
> thanks for testing this.  It works for me when executing as well.  But
> not when exporting.  Does that work for you?
>
> I have tested this on two computers with the latest git version.
>

Oh, I see, sorry I missed that in your original email.  I've just pushed
up change which should fix this issue.

Best -- Eric

>
> Cheers,
> Andreas
>
> Am 26.02.2011 01:29, schrieb Eric Schulte:
>> Hi Andreas,
>>
>> This exact example worked for me -- that is the results were returned
>> without executing the "sleep 5" code.
>>
>> Maybe you are using an old version of Org, or you have non-standard
>> default header argument values?
>>
>> Best -- Eric
>>
>> Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:
>>
>>   
>>> Hi all,
>>>
>>> When ':noweb yes' is in the header, ':cache yes' is ignored during
>>> export.  (At least when I export the sample file below.)
>>>
>>> To me this seems to be a bug.  Or am I missing something?
>>>
>>> Regards,
>>> Andreas
>>>
>>> PS: Example:
>>> ====================
>>> * Test
>>>   #+srcname: test_sleep
>>>   #+begin_src R :session :exports code
>>>     Sys.sleep(time=5)
>>>     1:10
>>>   #+end_src
>>>
>>>   #+srcname: test_sleep
>>>   #+begin_src R :session :exports results :noweb yes :cache yes
>>>     <<test_sleep>>
>>>   #+end_src
>>>
>>>   #+results[e2c9e6c2f84563b590a765502057d92463e50182]: test_sleep
>>>   |  1 |
>>>   |  2 |
>>>   |  3 |
>>>   |  4 |
>>>   |  5 |
>>>   |  6 |
>>>   |  7 |
>>>   |  8 |
>>>   |  9 |
>>>   | 10 |
>>> ==============================
>>>
>>>
>>> _______________________________________________
>>> Emacs-orgmode mailing list
>>> Please use `Reply All' to send replies to the list.
>>> Emacs-orgmode@gnu.org
>>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>>     
>> _______________________________________________
>> Emacs-orgmode mailing list
>> Please use `Reply All' to send replies to the list.
>> Emacs-orgmode@gnu.org
>> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>>   

      reply	other threads:[~2011-02-27 18:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24 18:07 [babel] Bug? :cache yes ignored when :noweb yes Andreas Leha
2011-02-26  0:29 ` Eric Schulte
2011-02-26 10:50   ` Andreas Leha
2011-02-27 18:03     ` Eric Schulte [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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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=87tyfp9wxj.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=andreas.leha@med.uni-goettingen.de \
    --cc=emacs-orgmode@gnu.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).