|
From: | Rick Frankel |
Subject: | Re: [O] [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 |
User-agent: | Roundcube Webmail/0.9.0 |
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
[Prev in Thread] | Current Thread | [Next in Thread] |