Re: [O] [bugs] Export to HTML requires issuing org-babel-execute-buffer; results replace fails

2012-01-28 Thread Leo Alekseyev
-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  

Re: [O] [bugs] Export to HTML requires issuing org-babel-execute-buffer; results replace fails

2012-01-27 Thread Eric Schulte
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:

Re: [O] [bugs] Export to HTML requires issuing org-babel-execute-buffer; results replace fails

2012-01-24 Thread Leo Alekseyev
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

Re: [O] [bugs] Export to HTML requires issuing org-babel-execute-buffer; results replace fails

2012-01-23 Thread Eric Schulte
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

Re: [O] [bugs] Export to HTML requires issuing org-babel-execute-buffer; results replace fails

2012-01-23 Thread Leo Alekseyev
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

Re: [O] [bugs] Export to HTML requires issuing org-babel-execute-buffer; results replace fails

2012-01-23 Thread Eric Schulte
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

Re: [O] [bugs] Export to HTML requires issuing org-babel-execute-buffer; results replace fails

2012-01-23 Thread Leo Alekseyev
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

[O] [bugs] Export to HTML requires issuing org-babel-execute-buffer; results replace fails

2012-01-20 Thread Leo Alekseyev
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