From: Eric Schulte <eric.schulte@gmx.com>
To: Leo Alekseyev <dnquark@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-babel order of evaluation
Date: Mon, 23 Jan 2012 10:56:19 -0700 [thread overview]
Message-ID: <87pqeas34l.fsf@gmx.com> (raw)
In-Reply-To: CADzxs1=juJXkwMHSN38SGay8KPMcS6DWv=j6NzTac6fszpcv7A@mail.gmail.com
Leo Alekseyev <dnquark@gmail.com> writes:
> On Thu, Jan 12, 2012 at 7:52 PM, Rick Frankel <rick@rickster.com> wrote:
>> On Thu, Jan 12, 2012 at 06:07:41PM -0700, Eric Schulte wrote:
>>> Rick Frankel <rick@rickster.com> writes:
>>>
>>> Turns out it was not that difficult to change this behavior. You and
>>> Leo are both correct that in-buffer-order evaluation is more natural and
>>> expected than the previous behavior. I've just pushed up a fix after
>>> which evaluating the following
>
> Eric,
> The fix doesn't seem to be working for me when I export the buffer to
> HTML.
My previous fix only set the order of evaluation for interactive buffer
evaluation. I've just pushed up another fix which sets the order of
evaluation during export.
Best,
> The ordering of call and source blocks once again becomes randomized,
> and in general, exported file is missing a bunch of stuff unless I run
> org-babel-execute-buffer prior to export. Since the export engine
> does its own evaluation, it doesn't seem like org-babel-execute-buffer
> should be a necessity. But I can't run org-babel-execute-buffer on
> anything with a src_<language> inline block as it gives me an error.
>
> I'm attaching two files which do not export correctly, at least when
> one doesn't run org-babel-execute-buffer; just do C-c C-e h and look
> at the output.
>
> --Leo
>
>
--
Eric Schulte
http://cs.unm.edu/~eschulte/
prev parent reply other threads:[~2012-01-23 18:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-12 0:25 org-babel order of evaluation Rick Frankel
2012-01-12 14:43 ` Eric Schulte
2012-01-12 22:35 ` Leo Alekseyev
2012-01-12 22:51 ` Rick Frankel
2012-01-13 1:07 ` Eric Schulte
2012-01-13 1:52 ` Rick Frankel
2012-01-20 17:58 ` Leo Alekseyev
2012-01-23 17:56 ` 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=87pqeas34l.fsf@gmx.com \
--to=eric.schulte@gmx.com \
--cc=dnquark@gmail.com \
--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).