From: Leo Alekseyev <dnquark@gmail.com>
To: Eric Schulte <eric.schulte@gmx.com>
Cc: Emacs orgmode <emacs-orgmode@gnu.org>
Subject: Re: [bugs] Export to HTML requires issuing org-babel-execute-buffer; results replace fails
Date: Mon, 23 Jan 2012 21:50:53 -0600 [thread overview]
Message-ID: <CADzxs1kKCuZqohS=A-nSwS=uW_nWoWrLdWMUZ+0dPY-t=+aLow@mail.gmail.com> (raw)
In-Reply-To: <87k44is34h.fsf@gmx.com>
On Mon, Jan 23, 2012 at 11:58 AM, Eric Schulte <eric.schulte@gmx.com> wrote:
> Leo Alekseyev <dnquark@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 you mean by "garbage" output?
That wasn't a very good description, sorry.
......
I just wrote a detailed description of the bug, and then remembered
that I forgot to copy the latest org pull into
/usr/share/emacs/24/lisp/org. This bug is now gone, probably as a
result of you fixing export evaluation order. However, the
description of "replace results" bug is still relevant. I'll denote
issues that are now fixed with appropriate markup.
#+BEGIN_MOOT_POINT
Take test-export4.org from my original message, and export (C-c C-e h;
don't evaluate the buffer beforehand). You will see the following
output: http://i.imgur.com/IM3oy.png
There are two problems:
(1) Notice that the output of _every_ src_R block is "images/conv2.png"
It should be "conv1.png" on the first invocation "conv2.png" on the
second, and "conv3.png" on the third.
(2) The last src_R block is not evaluated and, in fact, appears in the
output (which it shouldn't), mangled, as the underscore is taken as a
subscript.
#+END_MOOT_POINT
For comparison, if you first evaluate the buffer, and then export, you
will see this:
http://i.imgur.com/V6PXq.png
The output of the src_R blocks is now correct, but I don't see why one
needs to pre-evaluate the buffer to get correct output on export. The
overall output, as you can see, is _not_ correct, since the results
from invocation of src_R blocks via the export are _appended_ to those
that were generated via C-c C-v b.
>
> Could you isolate a minimal example demonstrating just the failure of
> results replacement?
Run the below code a few times with C-c C-v b, and you'll see
------------snip---------
#+property: session *R-babel*
#+NAME: foo
#+HEADER: :var plot.filename="conv1.png"
#+BEGIN_SRC R :results output silent
cat.fname.link <- function() { cat(plot.filename,"\n",sep="") }
cat.fname.link()
#+END_SRC
src_R[:results output replace]{ cat.fname.link() }
------------snip---------
You can also replace src_R with
#+begin_src R :results output raw replace :exports results
cat.fname.link()
#+end_src
and it will also fail to replace results.
All the above examples were run with the latest pull of org.
HTH,
--Leo
next prev parent reply other threads:[~2012-01-24 3:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-21 0:25 [bugs] Export to HTML requires issuing org-babel-execute-buffer; results replace fails Leo Alekseyev
2012-01-23 17:58 ` Eric Schulte
2012-01-24 3:50 ` Leo Alekseyev [this message]
2012-01-24 4:05 ` Eric Schulte
2012-01-24 4:53 ` Leo Alekseyev
2012-01-24 14:52 ` Eric Schulte
2012-01-24 23:35 ` Leo Alekseyev
2012-01-27 22:43 ` Eric Schulte
2012-01-28 23:07 ` Leo Alekseyev
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='CADzxs1kKCuZqohS=A-nSwS=uW_nWoWrLdWMUZ+0dPY-t=+aLow@mail.gmail.com' \
--to=dnquark@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=eric.schulte@gmx.com \
/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).