emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Andreas Leha <andreas.leha@med.uni-goettingen.de>
To: emacs-orgmode@gnu.org
Subject: Re: Naming a table produced by a CALL
Date: Mon, 27 Jan 2014 12:39:21 +0100	[thread overview]
Message-ID: <874n4pejrq.fsf@med.uni-goettingen.de> (raw)
In-Reply-To: 87eh3toit0.fsf@hornfels.zedat.fu-berlin.de

Hi Loris,

"Loris Bennett" <loris.bennett@fu-berlin.de> writes:

> Eric Schulte <schulte.eric@gmail.com> writes:
>
>> Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:
>>
>>> Hi Loris,
>>>
>>> "Loris Bennett" <loris.bennett@fu-berlin.de> writes:
>>>
>>>> Andreas Leha <andreas.leha@med.uni-goettingen.de> writes:
>>>>
>>>>> "Loris Bennett" <loris.bennett@fu-berlin.de> writes:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> I have a CALL which produces a table, which just gets the keyword
>>>>>> RESULT.  I would like to plot the data in the table with R and so would
>>>>>> like to refer to the data in the table.
>>>>>>
>>>>>> It seems I need to need to replace RESULT by NAME in
>>>>>> org-babel-results-keyword, but how do I pass the actual name?
>>>>>>
>>>>>> Cheers,
>>>>>>
>>>>>> Loris
>>>>>
>>>>> Make the CALL named:
>>>>>
>>>>> #+name: foo
>>>>> #+call: foo()
>>>>>
>>>>> HTH,
>>>>> Andreas
>
> This seems to break if I then try to reference the results of the call:
>
> #+NAME: test
> #+BEGIN_SRC sh
> echo a b c
> echo 1 2 3
> echo 4 5 6
> #+END_SRC
>
> #+NAME: call-test
> #+CALL: test() :results table :colnames yes
> #+RESULT: call-test
> | a | b | c |
> |---+---+---|
> | 1 | 2 | 3 |
> | 4 | 5 | 6 |
>
> #+NAME: r-test
> #+HEADER: :var data=call-test

I'd expect this to be call-test()
                               ^^
But it works for me with both call-test and call-test().
                               
> #+HEADER: :colnames yes
> #+BEGIN_SRC R
> data
> #+END_SRC
>
> #+RESULT: r-test
> | x   |
> |-----|
> | nil |
>
> Is it perhaps not clear whether "call-test" refers to the result or the
> call?  Or is my config broken?  I'm using version 
>
> 8.2.5g (8.2.5g-7-gb2dce8-elpaplus).
>
> Cheers,
>
> Loris
>

quick test on my setup with Org-mode version 8.2.4 (release_8.2.4-332-g7059d3):

--8<---------------cut here---------------start------------->8---
#+NAME: test
#+BEGIN_SRC sh
echo a b c
echo 1 2 3
echo 4 5 6
#+END_SRC

#+results: test
| a | b | c |
| 1 | 2 | 3 |
| 4 | 5 | 6 |

#+NAME: call-test
#+CALL: test() :results table :colnames yes

#+results: call-test
| a | b | c |
|---+---+---|
| 1 | 2 | 3 |
| 4 | 5 | 6 |


#+NAME: r-test
#+HEADER: :var data=call-test
#+HEADER: :colnames yes
#+BEGIN_SRC R
data
#+END_SRC

#+results: r-test
| a | b | c |
|---+---+---|
| 1 | 2 | 3 |
| 4 | 5 | 6 |
--8<---------------cut here---------------end--------------->8---

Are you sure about your '#+RESULT' ?

The default value for org-babel-results-keyword seems to be 'RESULTS'
with an 'S'.

(I have customized that to be lower case 'results'.)

Regards,
Andreas





>>>> Thanks.  In retrospect, that seems quite obvious.  Where is this
>>>> documented and should it be mentioned here:
>>>>
>>>> http://orgmode.org/manual/Evaluating-code-blocks.html
>>>>
>>>
>>> This is a 'not-so-old' feature.
>>
>> Yes, I believe this was added in the last month or two.
>>
>>> And I do not know whether it is documented at all.  I agree that
>>> 'Evaluating code blocks' is where the documentation should go.
>>>
>>
>> I'll happily apply a documentation patch.  I don't believe the copyright
>> assignment required for code contributions is required for contributions
>> to the documentation.
>>
>> Best,
>>
>>>
>>> Regards,
>>> Andreas
>>>
>>>
>>>> ?
>>>>
>>>> Cheers,
>>>>
>>>> Loris
>>>
>>>

  reply	other threads:[~2014-01-27 11:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-24 11:45 Naming a table produced by a CALL Loris Bennett
2014-01-24 13:03 ` Andreas Leha
2014-01-24 14:05   ` Loris Bennett
2014-01-25  9:44     ` Andreas Leha
2014-01-26 17:44       ` Eric Schulte
2014-01-27  9:50         ` Loris Bennett
2014-01-27 11:39           ` Andreas Leha [this message]
2014-01-27 13:01             ` Loris Bennett

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=874n4pejrq.fsf@med.uni-goettingen.de \
    --to=andreas.leha@med.uni-goettingen.de \
    --cc=emacs-orgmode@gnu.org \
    /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).