From: Eric Abrahamsen <firstname.lastname@example.org>
Subject: plotting tables
Date: Sun, 24 Mar 2013 14:44:12 +0800 [thread overview]
Message-ID: <email@example.com> (raw)
I'm trying to get my head around plotting data from org tables, for use
in LaTeX exports. I've been looking at these two pages:
As far as I can tell, there are two general approaches. One is an org
table with some #+PLOT declarations, and when I call `org-plot/gnuplot'
on it, gnuplot processes the table and shows it to me. Presumably I can
make it save to a file instead, I haven't investigated that yet.
The other approach seems to be using a named table, and then a gnuplot
source block that accepts the table data as a variable. In this case
you're writing an actual gnuplot script, rather than feeding gnuplot
options into a #+PLOT line.
1. Are these really mutually incompatible approaches, as they appear to
2. What's my best option if I want the following scenario: I start with
an org file containing an org table, call `org-latex-export-to-pdf' on
that file, get a coffee, and come back to find a nice pdf containing
just the plotted graph (no table). Can someone show me just the barest
3. I've been learning the tikz LaTeX package and am very impressed. Has
anyone used tikz/pgfplots with org?
In return, I promise to add a very hand-holdy explanation to worg,
provided that there isn't already one there that I missed.
next reply other threads:[~2013-03-24 6:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-24 6:44 Eric Abrahamsen [this message]
2013-03-24 10:42 ` plotting tables Dieter Wilhelm
2013-03-24 17:33 ` John Hendy
2013-03-26 3:09 ` Eric Abrahamsen
2013-03-26 15:19 ` John Hendy
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 \
* 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).