From: Aaron Ecay <aaronecay@gmail.com>
To: Sebastien Vauban <wxhgmqzgwmuf@spammotel.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Add 'inline-only option to org-export-babel-evaluate
Date: Thu, 18 Apr 2013 05:42:19 -0400 [thread overview]
Message-ID: <87vc7kqio4.fsf@gmail.com> (raw)
In-Reply-To: <86sj2okxfk.fsf@somewhere.org>
Hi Sebastien,
2013ko apirilak 18an, Sebastien Vauban-ek idatzi zuen:
>
> Hello,
>
> Bastien wrote:
>> I applied this patch, thanks a lot. Please see the small changes
>> I made to the ChangeLog entry for next commit messages:
>>
>> http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=25869e
>
> How is that suppose to cooperate with ":eval never-export" (which avoids all
> the evaluations during export)?
I could be wrong, but I don’t seem to see a convenient way to set this
header arg for both inline source blocks and #+call lines. These both
have no way of storing their results in a buffer, so in order to have
them be present in the export they must be evaluated every time.
On the other hand, it is not always desirable to call code blocks on
every export. They could be very time-consuming to compute. So, a way
to pick out the non-results-storing blocks is needed.
>
> I'm not sure to understand why this change is implemented as a variable which
> we would have to set up in our .emacs or bind in the file, instead of an
> header argument which we could set wherever we want (system-wide,
> language-specific, buffer-wide, subtree-wide, or code
> block-specific)...
What form would this take? Would we have a value of :eval which is
never-export-unless-inline?
--
Aaron Ecay
next prev parent reply other threads:[~2013-04-18 9:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 5:44 [PATCH] Add 'inline-only option to org-export-babel-evaluate Aaron Ecay
2013-04-01 7:45 ` Nicolas Goaziou
2013-04-01 15:10 ` Aaron Ecay
2013-04-02 22:14 ` Eric Schulte
2013-04-18 8:24 ` Aaron Ecay
2013-04-18 8:44 ` Bastien
2013-04-18 9:19 ` Sebastien Vauban
2013-04-18 9:42 ` Aaron Ecay [this message]
2013-04-18 10:19 ` Sebastien Vauban
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=87vc7kqio4.fsf@gmail.com \
--to=aaronecay@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=wxhgmqzgwmuf@spammotel.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).