emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Charles C. Berry" <ccberry@ucsd.edu>
To: Sebastien Vauban
Cc: Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: How to override ":eval no" in call lines?
Date: Fri, 23 Jan 2015 11:53:20 -0800	[thread overview]
Message-ID: <alpine.OSX.2.00.1501231149060.528@charles-berrys-macbook.local> (raw)
In-Reply-To: <86r3uln2lp.fsf@example.com>

On Fri, 23 Jan 2015, Sebastien Vauban wrote:

> "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.
> I don't get why one has to add ":eval yes" for both types of headers
> arguments.
> 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>
>    result
>  #+end_src
> which is evaluated in place.

No, like this:

#+begin_src emacs-lisp :var result=<NAME>[<INSIDE-HEADER-ARGS>](<ARGUMENTS>)

> Where do <END-HEADER-ARGS> fit into that picture?

Either before or after the :var ...



  reply	other threads:[~2015-01-23 19:53 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
2015-01-23 19:53       ` Charles C. Berry [this message]
     [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:

  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=alpine.OSX.2.00.1501231149060.528@charles-berrys-macbook.local \
    --to=ccberry@ucsd.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.org \


* 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).