emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rainer M Krug <Rainer@krugs.de>
To: emacs-orgmode@gnu.org
Subject: Re: Multiple (identical) RESULTS blocks of one code block?
Date: Tue, 10 Mar 2015 10:02:58 +0100	[thread overview]
Message-ID: <m2mw3l1ayl.fsf@krugs.de> (raw)
In-Reply-To: <87d24hmx2i.fsf@gmail.com> (Aaron Ecay's message of "Mon, 09 Mar 2015 23:05:38 -0300")

[-- Attachment #1: Type: text/plain, Size: 1912 bytes --]

Aaron Ecay <aaronecay@gmail.com> writes:

> Hi Rainer,
>
> 2015ko martxoak 9an, Rainer M Krug-ek idatzi zuen:
>>
>> Hi
>>
>> Consider the following:
>>
>> --8<---------------cut here---------------start------------->8---
>> * The calculation
>> #+NAME: testcode :exports both
>
> It looks like you’ve tried to put a header argument into the name.  Is
> it merely an accident?  I ask because...

Accident - the header argument should be behind the code block beginning
and not the NAME - sorry.

>
>> #+begin_src R  :session test
>> runif(10)
>> #+end_src
>>
>>
>> * summary of the results
>> First time
>> #+RESULTS: testcode :exports both
>> |  0.772744940361008 |
>> |  0.170518629485741 |
>> | 0.0833237133920193 |
>> |  0.149035625392571 |
>> |  0.698798568220809 |
>> |  0.627075897762552 |
>> |  0.177144371205941 |
>> | 0.0476319056469947 |
>> |  0.289851602632552 |
>> | 0.0296813279855996 |
>>
>> * and another
>> testthingy
>> #+RESULTS: testcode :exports both
>
> ...here it reoccurs, in identical format.  This is fine, interpreted
> as just a weird block name (and not as an actual header argument).
> But if you’re trying to allow the header arguments to vary for the two
> result blocks I don’t think it will be very nice.  (It would require
> re-evaluating the code block for each different combination of header
> arguments, which would give unexpected behavior in the case of side
> effects, etc. etc.)

I think I clud do this by using =#+CALL testcode= but this is not w=hat
I wanted.

>
> Maybe it’s not very important, but I just figured I’d ask for
> clarification.

Sure - I should be looking more carefully when typing.

Is my brain really that slow, as I am not a fast typer...

Cheers,

Rainer

>
> Thanks,
>
> --
> Aaron Ecay
>
>

-- 
Rainer M. Krug
email: Rainer<at>krugs<dot>de
PGP: 0x0F52F982

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 494 bytes --]

      reply	other threads:[~2015-03-10  9:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09 10:04 Multiple (identical) RESULTS blocks of one code block? Rainer M Krug
2015-03-09 13:01 ` John Kitchin
2015-03-09 13:10   ` Sebastien Vauban
2015-03-10  9:06   ` Rainer M Krug
2015-03-10  9:35     ` Rainer M Krug
     [not found]       ` <m2sidd2ems.fsf@andrew.cmu.edu>
2015-03-10 13:31         ` Rainer M Krug
2015-03-10 13:57           ` Rainer M Krug
2015-03-09 16:34 ` Nicolas Goaziou
2015-03-10  2:05 ` Aaron Ecay
2015-03-10  9:02   ` Rainer M Krug [this message]

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=m2mw3l1ayl.fsf@krugs.de \
    --to=rainer@krugs.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).