From: Eric Schulte <schulte.eric@gmail.com>
To: Michael Brand <michael.ch.brand@gmail.com>
Cc: Org Mode <emacs-orgmode@gnu.org>
Subject: Re: evaluation context in call statements
Date: Mon, 01 Jul 2013 07:11:51 -0600 [thread overview]
Message-ID: <87hagejug8.fsf@gmail.com> (raw)
In-Reply-To: <CALn3zogRv7VPkMgHY=y--CPb1WJvyGwoyZGSAuJgSqAksa9Y9w@mail.gmail.com> (Michael Brand's message of "Mon, 1 Jul 2013 12:23:14 +0200")
Michael Brand <michael.ch.brand@gmail.com> writes:
> Hi Eric
>
> On Mon, Jul 1, 2013 at 12:24 AM, Eric Schulte <schulte.eric@gmail.com> wrote:
>> I've just pushed up a patch which implements this change. Call lines
>> should now work exactly as named code blocks providing clarity,
>> uniformity and the flexibility to run multiple identical call lines.
>
> This is very useful for me sometimes, thank you.
>
> I am now adapting my recent ERT that you disabled in the meantime due
> to your changes and therefore have a question. With C-c C-c on this
> call line
>
> #+NAME: src_block_location_shell sect call
> #+CALL: src_block_location_shell()
>
> the result is
>
> #+RESULTS: src_block_location_shell sect call
> : shell a:1, b:0, c:3, d:0, e:0
>
> as expected. With org-test-with-expanded-babel-code I would expect the
> same but get
>
> #+RESULTS:
> : shell a:1, b:0, c:3, d:0, e:0
>
> Should the behavior of org-test-with-expanded-babel-code not be
> aligned?
>
Thanks for catching this.
The export function (used by `org-test-with-expanded-babel-code') hadn't
been updated to use call line names. I've just pushed up a fix.
Best,
--
Eric Schulte
http://cs.unm.edu/~eschulte
next prev parent reply other threads:[~2013-07-01 13:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-25 17:34 evaluation context in call statements Rick Frankel
2013-06-25 19:21 ` Achim Gratz
2013-06-25 19:53 ` Achim Gratz
2013-06-25 20:06 ` Achim Gratz
2013-06-25 20:07 ` Michael Brand
2013-06-25 20:20 ` Achim Gratz
2013-06-25 20:55 ` Achim Gratz
2013-06-25 22:41 ` Eric Schulte
2013-06-26 6:29 ` Achim Gratz
2013-06-26 14:38 ` Rick Frankel
2013-06-26 15:13 ` Nicolas Goaziou
2013-06-26 15:29 ` Rick Frankel
2013-06-26 15:49 ` Eric Schulte
2013-06-26 15:06 ` Eric Schulte
2013-06-27 4:55 ` Achim Gratz
2013-06-27 6:22 ` Andreas Leha
2013-06-27 14:27 ` Achim Gratz
2013-06-27 23:12 ` Andreas Leha
2013-06-30 22:24 ` Eric Schulte
2013-07-01 10:23 ` Michael Brand
2013-07-01 13:11 ` Eric Schulte [this message]
2013-07-01 13:52 ` Michael Brand
2013-07-01 14:10 ` Eric Schulte
2013-06-26 8:38 ` Michael Brand
2013-06-26 14:54 ` Eric Schulte
2013-06-26 16:53 ` Michael Brand
2013-06-26 17:11 ` Eric Schulte
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=87hagejug8.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=michael.ch.brand@gmail.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).