From: Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: How to override ":eval no" in call lines?
Date: Thu, 22 Jan 2015 09:28:14 +0100 [thread overview]
Message-ID: <86lhkv1aox.fsf@example.com> (raw)
In-Reply-To: 86oaq02ivd.fsf@example.com
Hello,
May I bump up this thread?
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.
>
> Export this ECM (to HTML, for example) and see for yourself that it does
> not seem evident...
>
> #+TITLE: ECM to be exported
>
> #+PROPERTY: eval no
> #+PROPERTY: results none
>
> * Results
> :PROPERTIES:
> :exports: results
> :results: replace
> :END:
>
> ** Square
>
> Here nothing gets executed: neither the code block, nor the call lines...
>
> #+name: square
> #+begin_src emacs-lisp :tangle no :var x=1
> (* x x)
> #+end_src
>
> 2 x 2 = call_square(x=2).
>
> 3 x 3 = call_square[:eval yes](x=3).
>
> ** Plus
>
> Here, ":eval yes" (or even ":eval foo" FWIW) allows the code block to get
> executed at export:
>
> #+name: plus
> #+begin_src emacs-lisp :tangle no :var x=4 :eval foo
> (+ x x)
> #+end_src
>
> But none of the call lines gets executed...
>
> 5 + 5 = call_plus(x=5).
>
> 6 + 6 = call_plus[:eval yes](x=6).
>
> So, how do I override the ":eval no" specified at the file level?
>
> Any idea?
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2015-01-22 8:28 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 [this message]
2015-01-22 16:50 ` Charles C. Berry
2015-01-23 11:44 ` Sebastien Vauban
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
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=86lhkv1aox.fsf@example.com \
--to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).