From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-export-babel-evaluate and :exports none
Date: Wed, 20 Feb 2013 16:31:37 +0100 [thread overview]
Message-ID: <877gm33sti.fsf@gmail.com> (raw)
In-Reply-To: <87a9r1z74c.fsf@Rainer.invalid> (Achim Gratz's message of "Mon, 18 Feb 2013 21:42:27 +0100")
Hello,
Achim Gratz <Stromeko@nexgo.de> writes:
> Nicolas Goaziou writes:
>> I confirm the problem. It is coming from
>> 12d592b73223f3b0628e10f0f627447b1a312203. I reverted it.
>
> Doesn't this throw the baby out with the bathtub? If anything that's an
> indication that the evaluation and the exporting of a block should be
> independently controllable. So either org-babel-exp-process-buffer is
> not the correct function to call or it needs to take
> org-export-babel-evaluate into account.
I'm just starting over because that wasn't a correct solution. I'm not
even sure about what bug this patch fixed.
Anyway, it isn't org-export-babel-evaluate's job to tell when to
evaluate a source code block. It may be org-babel-exp-process-buffer's.
I asked the author of that patch to provide more information about the
context so I can get a clue.
> BTW, the function org-export-execute-babel-code is called before it is
> being defined. Not sure why this doesn't give a warning.
Why should it? It's not a macro, after all.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-02-20 15:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-17 14:24 org-export-babel-evaluate and :exports none Ista Zahn
2013-02-18 18:22 ` Ista Zahn
2013-02-18 18:59 ` Jay Kerns
2013-02-18 19:20 ` Ista Zahn
2013-02-18 20:17 ` Nicolas Goaziou
2013-02-18 20:26 ` Ista Zahn
2013-02-18 20:42 ` Achim Gratz
2013-02-20 15:31 ` Nicolas Goaziou [this message]
2013-02-22 20:49 ` Achim Gratz
2013-02-22 21:42 ` Ista Zahn
2013-02-23 8:08 ` Nicolas Goaziou
2013-02-23 8:45 ` Achim Gratz
2013-02-18 20:49 ` Achim Gratz
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=877gm33sti.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=Stromeko@nexgo.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).