From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rick Frankel Subject: Re: [babel] Problems assigning tables as variables using #+CALL and using properties in code blocks and sbe calls Date: Fri, 19 Jul 2013 13:56:53 -0400 Message-ID: <662b2ff54a06a6fd83efd44979094d91@mail.rickster.com> References: <871u6ve4tr.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50871) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V0EvI-0006VO-8r for emacs-orgmode@gnu.org; Fri, 19 Jul 2013 13:56:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1V0EvF-0005YY-AP for emacs-orgmode@gnu.org; Fri, 19 Jul 2013 13:56:56 -0400 Received: from [204.62.15.78] (port=34799 helo=mail.rickster.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1V0EvF-0005YS-61 for emacs-orgmode@gnu.org; Fri, 19 Jul 2013 13:56:53 -0400 In-Reply-To: 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: Torsten Wagner Cc: Org Mode Mailing List , Eric Schulte On 2013-07-19 11:57, Torsten Wagner wrote: > Hi Eric, > > one mini-step forward. > The #+CALL function does not work if the table has a horizontal line > like in > #+TBLNAME: othertablename > | a | b | c | d | > |---+---+---+---| > | 4 | 3 | 2 | 1 | > | z | x | y | w | > > however, it works for > > #+TBLNAME: othertablename > | a | b | c | d | > | 4 | 3 | 2 | 1 | > | z | x | y | w | > > I guess we come closer to the problem ;) > This is, i believe related to the general problems I have been seeing with the processing of tables passed as arguments to babel blocks vs. the same tables passed to `call' lines. For example: #+BEGIN_ORG #+name: ptable | head1 | head2 | |-------+-------| | a | 1 | | b | 2 | #+name: ptable-mirror #+BEGIN_SRC python :var t=ptable :results value :colnames no return t #+END_SRC #+RESULTS: ptable-mirror | head1 | head2 | | a | 1 | | b | 2 | #+call: ptable-mirror() #+RESULTS: | head1 | head2 | | a | 1 | | b | 2 | #+call: ptable-mirror(t=ptable) #+RESULTS: | head1 | head2 | |-------+-------| | a | 1 | | b | 2 | #+END_ORG As you can see, the handling of headers/colnames is different in a `call' depending on if the argument is specified explicitly or not. BTW, changing `colnames no' to `:colnames yes' results in: #+BEGIN_ORG #+call: ptable-mirror(t=ptable) #+RESULTS: | head1 | head2 | |-------+-------| | head1 | head2 | |-------+-------| | a | 1 | | b | 2 | #+END_ORG rick