emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Eric Schulte <schulte.eric@gmail.com>
To: Suvayu Ali <fatkasuvayu+linux@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Unexpected behaviour with gnuplot source blocks
Date: Fri, 21 Jun 2013 10:07:39 -0600	[thread overview]
Message-ID: <87ppvfqwfo.fsf@gmail.com> (raw)
In-Reply-To: <20130621154231.GA17660@kuru.dyndns-at-home.com> (Suvayu Ali's message of "Fri, 21 Jun 2013 17:42:31 +0200")

Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:

> On Fri, Jun 21, 2013 at 09:02:28AM -0600, Eric Schulte wrote:
>> 
>> I've added a customization variable to ob-gnuplot which may be used to
>> map file extensions to terminals.  Currently it just holds the mapping
>> from eps to "postscript eps"
>> 
>>     ;; -*- emacs-lisp -*-
>>     (defcustom *org-babel-gnuplot-terms*
>>       '((eps . "postscript eps"))
>>       "List of file extensions and the associated gnuplot terminal."
>>       :group 'org-babel
>>       :type '(repeat (cons (symbol :tag "File extension")
>>                            (string :tag "Gnuplot terminal"))))
>> 
>
> Great idea!
>

Thanks, I hope it is useful.

>
>> If anyone knows of other good default mapping to add please let me know.
>> 
>
> I personally use "pdfcairo color" for pdf output.

This is already the default behavior for "term pdf" on my system, so I
don't think we need to add it to the list.  I did just add some logic to
ensure that output terminals are closed at the end of code blocks, which
was required for a simple pdf example to work for me.

Cheers,

-- 
Eric Schulte
http://cs.unm.edu/~eschulte

next prev parent reply	other threads:[~2013-06-21 16:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-18 14:52 Unexpected behaviour with gnuplot source blocks Christopher Witte
2013-06-20 16:12 ` Eric Schulte
2013-06-21 11:17   ` Christopher Witte
2013-06-21 15:02     ` Eric Schulte
2013-06-21 15:42       ` Suvayu Ali
2013-06-21 16:07         ` Eric Schulte [this message]
2013-06-21 16:15           ` Suvayu Ali
2013-06-22 16:02       ` Achim Gratz
2013-06-22 20:10         ` Eric Schulte

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

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