From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Leha Subject: Re: [babel] howto debug #+call lines Date: Fri, 05 Oct 2012 23:06:43 +0200 Message-ID: <87k3v4tyqk.fsf@med.uni-goettingen.de> References: <87pq4ztgkg.fsf@med.uni-goettingen.de> <87pq4x8www.fsf@gmx.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:55351) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TKF6q-0000B8-1w for emacs-orgmode@gnu.org; Fri, 05 Oct 2012 17:07:00 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TKF6o-00076f-PN for emacs-orgmode@gnu.org; Fri, 05 Oct 2012 17:06:59 -0400 Received: from plane.gmane.org ([80.91.229.3]:60404) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TKF6o-00076b-Ix for emacs-orgmode@gnu.org; Fri, 05 Oct 2012 17:06:58 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1TKF6t-0005Er-5t for emacs-orgmode@gnu.org; Fri, 05 Oct 2012 23:07:03 +0200 Received: from vpn-2053.gwdg.de ([134.76.2.53]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 05 Oct 2012 23:07:03 +0200 Received: from andreas.leha by vpn-2053.gwdg.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Fri, 05 Oct 2012 23:07:03 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Hi Eric, > Andreas Leha 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? >> >> Regards, >> Andreas >> > > 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) > results > #+end_src 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 block? 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] data.frame(x=a) #+end_src --- Regards, Andreas