From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
Subject: Re: How to override ":eval no" in call lines?
Date: Fri, 23 Jan 2015 12:44:18 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
"Charles C. Berry" wrote:
> Sebastien Vauban wrote:
>> In a long document, I must have ":eval no" at file level, as this is
>> the common setting for most code blocks. However, how do I unset that
>> for some call lines.
> See (info "(org) Evaluating code blocks")
> Note what it says about 'inside' and 'outside' header arguments. You
> need *both* set to `:eval yes'.
> The inside arg will allow execution of `plus' while the `outside' will
> allow execution of call_plus(...).
> Try this:
> 6 + 6 = call_plus[:eval yes](x=6)[:eval yes].
That works, thanks!
However, I really have trouble understanding what are inside and outside
header arguments for. I still don't get it properly.
Summarizing the above doc:
- "inside" header arguments are applied to the *evaluation of the code
block*. They /affect how the code block is evaluated/.
- "end" header arguments do not affect evaluation of the named code
block; instead, they /affect how the results are incorporated/ into
the Org mode buffer.
I don't get why one has to add ":eval yes" for both types of headers
Moreover, I once read that when evaluating a call line, it is converted
into an ephemeral Emacs Lisp code block equivalent to the call line (and
created at the point of the call line):
#+begin_src emacs-lisp :var result=<NAME>(<ARGUMENTS>) <INSIDE-HEADER-ARGS>
which is evaluated in place.
Where do <END-HEADER-ARGS> fit into that picture?
next prev parent reply other threads:[~2015-01-23 11:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 14:55 How to override ":eval no" in call lines? Sebastien Vauban
2015-01-22 8:28 ` Sebastien Vauban
2015-01-22 16:50 ` Charles C. Berry
2015-01-23 11:44 ` Sebastien Vauban [this message]
2015-01-23 19:53 ` Charles C. Berry
[not found] ` <alpine.OSX.2.00.1501231149060.528-iDQ3frm8jJiryYnjg5slPZa4wMfmKMrbhPhL2mjWHbk@public.gmane.org>
2015-02-09 14:43 ` Sebastien Vauban
2015-02-09 17:54 ` Charles C. Berry
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).