From: Dan Davison <dandavison7@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [babel] Producing figures from octave
Date: Wed, 31 Aug 2011 20:47:04 -0700 [thread overview]
Message-ID: <m1vctcrkjr.fsf@gmail.com> (raw)
In-Reply-To: CAJ+2YJMD=G9YxFkKYWjdU=1GmE5wdFH+3yD1PEUuc9o4TpuSMA@mail.gmail.com
Ethan Ligon <ligon@are.berkeley.edu> writes:
> Dan Davison has a brief worg tutorial on using babel with octave at
>
> http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-octave-matlab.html
>
Hi Ethan,
> Amongst other things, he offers the following example block for
> producing a figure:
(Actually, the example is not by me.)
> #+begin_src octave :output file :file chart.png
> figure( 1, "visible", "off" );
> sombrero;
> print -dpng chart.png
> #+end_src
:output file is wrong (there's no header arg named :output).
:file chart.png says to write the results to that file. The "results"
are whatvever the variable `ans` holds at the end of the block, and I
think that must be the file path you're seeing.
One way to write that example is:
#+begin_src octave :results file
figure( 1, "visible", "off" );
sombrero;
print -dpng chart.png;
ans = "chart.png";
#+end_src
:results file says to interpret the result as a file path.
I've updated the worg page.
Dan
> However, rather than delivering the png figure, the file chart.png
> consists solely of the string "/usr/share/octave/packages/3.2". I'm
> not sure where this string is coming from:
> it's *not* part of the
> stuff that octave writes to stdout when the interpreter is invoked (my
> first guess).
>
> I suspect that the options that need to be offered on the #+begin_src
> line have changed somehow since that worg page was last updated at the
> end of April of this year, but don't really know.
>
> Help!
> -Ethan
prev parent reply other threads:[~2011-09-01 3:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-31 21:36 [babel] Producing figures from octave Ethan Ligon
2011-09-01 3:47 ` Dan Davison [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=m1vctcrkjr.fsf@gmail.com \
--to=dandavison7@gmail.com \
--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).