emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Schulte <schulte.eric@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [babel] how to pass data to gnuplot from another block
Date: Thu, 05 Dec 2013 11:29:15 -0700	[thread overview]
Message-ID: <87siu7883o.fsf@gmail.com> (raw)
In-Reply-To: 87vbz3lpi8.fsf@ucl.ac.uk

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> Eric Schulte <schulte.eric@gmail.com> writes:
>> Hi Eric,
>> The attached works fine for me (using sh since I don't have octave).
> Dear Eric,
> thanks for your quick reply and sorry for taking so long to get back to
> you.  I ended up going to Chile for a week the day after sending my
> original email and had very little Internet access (and, actually, no
> time even if I had had proper connectivity).  Back now!
> [...]
>> Ensure that the data you're passing into gnuplot is a table and not a
>> string.  Gnuplot blocks handle tables by writing them to a file, and
>> then replacing the variable with the file name.  As I recall gnuplot
>> blocks assume string data already is a file name, so the variable is
>> replaced directly.
> Ah ha, this is a subtle one!  The output looks the same in either case,
> as Nick D. also notes.  By changing the results generated to value and
> not output and adding an expression at the end of my octave code to
> generate the value required got things working.
> The subtlety makes this a rather frustrating experience, however.  Is
> there any way to convince babel to treat a string output as an org table
> so that subsequent chaining works in this case as well?

I'm not familiar with ob-octave, but I'd imagine ":results vector"
should do the trick.  If not then it might be worth adding something
like the following (borrowed from ob-sh.el) to ob-octave.

    (org-babel-result-cond (cdr (assoc :result-params params))
      (let ((tmp-file (org-babel-temp-file "sh-")))
        (with-temp-file tmp-file (insert results))
        (org-babel-import-elisp-from-file tmp-file)))


> Thanks again,
> eric

Eric Schulte
PGP: 0x614CA05D

  reply	other threads:[~2013-12-05 18:38 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-22  9:57 [babel] how to pass data to gnuplot from another block Eric S Fraga
2013-11-22 15:00 ` Eric Schulte
2013-11-22 17:27   ` Nick Dokos
2013-11-23 16:15     ` Eric Schulte
2013-12-13 15:23       ` Greg Troxel
2013-12-13 15:30         ` Eric Schulte
2013-12-13 15:48           ` Greg Troxel
2013-12-13 16:20             ` Eric Schulte
2013-12-13 17:13               ` Eric Schulte
2013-12-13 19:32                 ` Nick Dokos
2013-12-13 22:40                 ` Achim Gratz
2013-12-13 23:18                 ` Eric Schulte
2013-12-14 10:21                   ` Achim Gratz
2013-12-13 18:38               ` Greg Troxel
2013-12-13 19:08                 ` Sebastien Vauban
2013-12-13 16:32           ` Achim Gratz
2013-12-05  7:35   ` Eric S Fraga
2013-12-05 18:29     ` Eric Schulte [this message]
2013-12-05 19:59       ` Eric S Fraga
2013-12-06  2:06         ` Eric Schulte
2013-12-06 11:59           ` Eric S Fraga

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:

  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=87siu7883o.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).