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

From: Eric Schulte <schulte.eric@gmail.com>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Unexpected behaviour with gnuplot source blocks
Date: Sat, 22 Jun 2013 14:10:26 -0600	[thread overview]
Message-ID: <8761x5zfey.fsf@gmail.com> (raw)
In-Reply-To: <87vc56w2v5.fsf@Rainer.invalid> (Achim Gratz's message of "Sat, 22 Jun 2013 18:02:06 +0200")

Achim Gratz <Stromeko@nexgo.de> writes:

> Eric Schulte writes:
>>> #+BEGIN_SRC gnuplot :file test.eps
>>>   reset
>>       ^
>>   WRT |, I've also added the *org-babel-gnuplot-prefix* variable, which
>> may be set to e.g., "reset" to reset the gnuplot process between code
>> blocks.
>
> We have recently introduced similar functionality in ob-perl and it
> probably deserves a more general treatment and easier customization.
> Doing these things with defcustoms or defvars should be shunned, since
> it makes Org files using these options inherently unportable and
> non-self-contained.
>

Agreed.

>
> For the functionality that is implemented here, I'd think two new
> general header arguments are appropriate, namely :prolog and :epilog,

I've added prologue and epilogue header arguments.  They are implemented
for gnuplot and any language which uses `org-babel-expand-body:generic'.

The particular case of closing the gnuplot output terminal does not use
the epilogue, but rather happens automatically only in those cases in
which the output is explicitly set.

> 
> which should take the name of a source block (same language), a
> literal string in quotes, the result of an inline call of another
> source block and inline elisp (the result of execution must be in the
> appropriate syntax) as an argument.  We might need some friendlier way
> than elisp if we want to use URL (esp. file:…) in the same capacity.
> For session execution there may be a need to distibguish between the
> session start, subsequent invocations and perhaps closing of the
> session (we don't have that at the moment, I think).
>

I think standard header arguments should suffice.

Thanks,

>
>
> Regards,
> Achim.

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

     prev parent reply	other threads:[~2013-06-23  3:16 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
2013-06-21 16:15           ` Suvayu Ali
2013-06-22 16:02       ` Achim Gratz
2013-06-22 20:10         ` Eric Schulte [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=8761x5zfey.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=Stromeko@nexgo.de \
    --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

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