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

From: "Eric Schulte" <schulte.eric@gmail.com>
To: Austin Frank <austin.frank@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [babel] exports, caching, remote execution
Date: Thu, 17 Jun 2010 07:42:46 -0700	[thread overview]
Message-ID: <87eig5en4p.fsf@gmail.com> (raw)
In-Reply-To: <m0typ2jgh5.fsf@gmail.com> (Austin Frank's message of "Thu, 17 Jun 2010 02:55:18 -0400")

Hi Austin,

Austin Frank <austin.frank@gmail.com> writes:

> Hey all--
>
> Two (hopefully quick) questions:
>
> 1) Does the exporter respect the :cache argument?  When I evaluate a
>    buffer, I can tell that cached blocks are not re-run, as expected.
>    When I export to \LaTeX or PDF, it seems that all blocks in the file
>    are re-run.  Is there a way to force the exporter to respect caching?
>

I believe the exporter does respect caching, the following minimal
example worked (i.e. was not re-run) for me on export to html.  Could
you provide an example that demonstrates the problem?

--8<---------------cut here---------------start------------->8---
** cache on export
do we export cached blocks

#+begin_src sh :cache yes :exports results
  date
#+end_src

#+results[06ed73c6d8d022cf9c323d92af885952865add17]:
: Thu Jun 17 07:35:19 PDT 2010
--8<---------------cut here---------------end--------------->8---

>
> 2) Is there a way to generate graphical output on a remote host and
>    still have it included in export?

Not that I'm currently aware of.  Dan has handled most of the remote
execution work so he may know more than me in this regard.

>    A block like
>
>    #+source: rplot
>    #+BEGIN_SRC R :exports results :dir /user@example.com: :file test.png
>    plot(my-object)
>    #+END_SRC
>    
>    Gives me
>    
>    #+results:
>    [[file:/scpc:user@example.com:/users/home/user/test.png]]
>

Is "scpc" in the line above a transport protocol?  Maybe this should be
an org-mode wide features, i.e. the ability to resolve remote file
references with C-c C-o and on export.  Does that sound reasonable, and
would it take care of the need in this particular case?

>
>    When I export to latex or pdf, the graphic isn't included because
>    the file for export is local but the graphic is remote.  Is there a
>    way to include remotely generated graphics in a locally exported
>    file?  Something like downloading via scp before exporting?
>

A block like the following may be an acceptable workaround in the near
term (notice I named your block above).

#+begin_src sh :file test.png :var remote=rplot :exports results
  scp $remote ./test.png
#+end_src

>
>
> Thanks for any help,
> /au

Thanks -- Eric

next prev parent reply	other threads:[~2010-06-17 14:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-17  6:55 [babel] exports, caching, remote execution Austin Frank
2010-06-17 14:42 ` Eric Schulte [this message]
2010-06-17 19:29   ` Austin Frank
2010-06-18 15:35   ` David Maus
2010-08-19 20:59   ` Tom Short
2010-08-25 18:04     ` Eric Schulte
2010-09-19  2:11     ` 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=87eig5en4p.fsf@gmail.com \
    --to=schulte.eric@gmail.com \
    --cc=austin.frank@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

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