From: suvayu ali <fatkasuvayu+linux@gmail.com>
To: John Hendy <jw.hendy@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Gnuplot best practice?
Date: Fri, 6 Aug 2010 17:53:32 -0700 [thread overview]
Message-ID: <AANLkTikiL7RevrG1FLPMUFu=MSBcz-_dddMWWxGEQSV_@mail.gmail.com> (raw)
In-Reply-To: <AANLkTi=aSZfcG838YApUioqbU-+rL1BH0QHA=V-RfLsQ@mail.gmail.com>
Hello,
On 6 August 2010 16:11, John Hendy <jw.hendy@gmail.com> wrote:
> Hi,
>
> I've been hunting for some info on gnuplot and wondered if there is a
> suggested "best practice" for using it and org...
> I've just used what worg has (#+PLOT: ...)
> - http://orgmode.org/worg/org-tutorials/org-plot.php
>
> But several discussions seem to show a lot of people using embedded source
> instead (#+begin_src gnuplot...)?
> - http://www.mail-archive.com/emacs-orgmode@gnu.org/msg26014.html
> - http://www.mail-archive.com/emacs-orgmode@gnu.org/msg27861.html
> - http://www.mail-archive.com/emacs-orgmode@gnu.org/msg28119.html
> Is it better to choose one over the other? I'm guessing it's easier to find
> help with the babel method since the lingo is the same vs. needing to know
> the discrepancies used by org-plot to translate into gnuplot?
>
I have been using both org-plot/gnuplot and ob-gnuplot lately. I found
#+PLOT directives very useful to get a few quick interactive plots
while I am playing with things. But for publication quality plots I
find org-babel much more flexible and capable. Also org-plot has
certain limitations, e.g. it can't make plots with error bars.
> Thanks for suggestions,
> John
GL
--
Suvayu
Open source is the future. It sets us free.
prev parent reply other threads:[~2010-08-07 0:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 23:11 Gnuplot best practice? John Hendy
2010-08-07 0:53 ` suvayu ali [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='AANLkTikiL7RevrG1FLPMUFu=MSBcz-_dddMWWxGEQSV_@mail.gmail.com' \
--to=fatkasuvayu+linux@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jw.hendy@gmail.com \
/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).