-snip--
#+property: session *R-babel*
#+NAME: foo
#+HEADER: :var a=a1.png
#+BEGIN_SRC R :results output silent
cat(in foo block\n)
cat.a - function() { cat(a,\n,sep=) }
cat.a()
#+END_SRC
#+call: foo(a=a1.png)
#+begin_src R :results output raw replace :exports results
Leo Alekseyev dnqu...@gmail.com writes:
If /inline blocks/ above don't replace their results above then that is
expected. If you can find instances where call lines or blocks don't
replace their results then that is a bug.
Yes, I was finding that neither inline nor regular blocks replace:
If /inline blocks/ above don't replace their results above then that is
expected. If you can find instances where call lines or blocks don't
replace their results then that is a bug.
Yes, I was finding that neither inline nor regular blocks replace: run
the following with C-c C-v b a few
Leo Alekseyev dnqu...@gmail.com writes:
Since all source blocks are evaluated on export, I don't think it
should be necessary to issue org-babel-execute-buffer before invoking
export. However, running HTML export without org-babel-execute-buffer
currently produces garbage output.
What do
On Mon, Jan 23, 2012 at 11:58 AM, Eric Schulte eric.schu...@gmx.com wrote:
Leo Alekseyev dnqu...@gmail.com writes:
Since all source blocks are evaluated on export, I don't think it
should be necessary to issue org-babel-execute-buffer before invoking
export. However, running HTML export
Leo Alekseyev dnqu...@gmail.com writes:
On Mon, Jan 23, 2012 at 11:58 AM, Eric Schulte eric.schu...@gmx.com wrote:
Leo Alekseyev dnqu...@gmail.com writes:
Since all source blocks are evaluated on export, I don't think it
should be necessary to issue org-babel-execute-buffer before invoking
On Mon, Jan 23, 2012 at 10:05 PM, Eric Schulte eric.schu...@gmx.com wrote:
Leo Alekseyev dnqu...@gmail.com writes:
On Mon, Jan 23, 2012 at 11:58 AM, Eric Schulte eric.schu...@gmx.com wrote:
Leo Alekseyev dnqu...@gmail.com writes:
Since all source blocks are evaluated on export, I don't think
Since all source blocks are evaluated on export, I don't think it
should be necessary to issue org-babel-execute-buffer before invoking
export. However, running HTML export without org-babel-execute-buffer
currently produces garbage output.
On the other hand, I have several examples where