From: Andreas Leha <email@example.com>
Subject: Re: [babel] howto debug #+call lines
Date: Mon, 08 Oct 2012 14:35:17 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
> Andreas Leha <email@example.com> writes:
>> Hi Eric,
>>> Andreas Leha <firstname.lastname@example.org> writes:
>>>> Hi all,
>>>> I am getting different results from the evaluation of a source block and
>>>> the evaluation of a #+call line to that block.
>>>> Therefore, my question: Is there an equivalent to
>>>> org-babel-expand-src-block (C-c C-v v) for #+call lines?
>>>> Or more general: How do I debug #+call lines?
>>> Can you provide a minimal example?
>>> You could write a code block equivalent to the call line. E.g.,
>>> #+call: foo(bar=1)
>>> is equivalent to
>>> #+begin_src emacs-lisp :var results=foo(bar=1)
>> Thanks for following this up. I found the problem in my case: The
>> header argument ':colnames yes' was missing from the call line, such that
>> the passed variables were different. (I've fallen into that trap
>> repeatedly, but do not learn, as it seems...)
>> It would have been a lot easier to find this, if I had had the possibility
>> to do C-c C-v v on the call line to get the chance to step through the
>> (R-) code that is evaluated. Without this, it took me some time to
>> figure things out.
>> So the question still stands: Is there the possibility to see what is
>> actually executed with a call line, similar to C-c C-v v on a source
> There is no body to expand in a call line so C-c C-v v would have
> nothing to show. You can however jump to the related code block and
> call C-c C-v v there. This process could be made faster by wrapping the
> org-babel-goto-named-src-block and org-babel-expand-src-block functions
> into a single function.
>> For a small example consider:
>> #+name: foo
>> | bar |
>> | baz |
>> | bam |
>> #+call: testblock[:var a=foo]() :colnames yes
>> #+name: testblock
>> #+begin_src R :var a=foo :colnames yes
>> a <- a[,1]
Thanks for the confirmation, that there is no possibility to expand a
I know, that I can jump to the code block and expand that one (quite
fast with C-c C-v g RET C-c C-v v), but that is exactly *not* what I was
looking for. Because then, the header arguments to the source code
block will apply instead of the header arguments to the #+call line.
I was hoping for a C-c C-v v on #+call lines, which would spare me from
modifying the source block's header arguments. But it is not a pressing
issue, just my laziness (and bad coding perhaps).
next prev parent reply other threads:[~2012-10-08 12:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 21:02 [babel] howto debug #+call lines Andreas Leha
2012-10-05 2:39 ` Eric Schulte
2012-10-05 21:06 ` Andreas Leha
2012-10-07 1:03 ` Eric Schulte
2012-10-08 12:35 ` Andreas Leha [this message]
2012-10-09 2:31 ` Eric Schulte
2012-10-09 16:15 ` Andreas Leha
2012-10-03 21:07 Andreas Leha
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).