From: Brett Viren <bv@bnl.gov>
To: henry atting <nsmp_06@online.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: python/babel inline images
Date: Tue, 05 Jun 2012 08:46:18 -0400 [thread overview]
Message-ID: <ir47gvm9bad.fsf@lycastus.phy.bnl.gov> (raw)
In-Reply-To: <87pq9egifm.fsf@bye.fritz.box> (henry atting's message of "Tue, 05 Jun 2012 12:30:05 +0200")
[-- Attachment #1: Type: text/plain, Size: 692 bytes --]
henry atting <nsmp_06@online.de> writes:
> I do not succeed in generating an inline image as a result of a
> python code block. The code itself works, C-c C-c generates the
> according picture, but only in my home directory. The code block:
Could you not just follow the block with a hand-written link to the
output file? Then, when it becomes available toggle "C-c C-x C-v" (once
or twice) or "M-x org-display-inline-images" once.
Maybe also rewrite the Python to place the output SVG in a directory
associated with your ORG file so that link can be relative. I simply
use an env. var. to locate where my plots should output.
I'm an org-newbie so maybe there are better ways.
-Brett.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2012-06-05 12:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 10:30 python/babel inline images henry atting
2012-06-05 12:46 ` Brett Viren [this message]
2012-06-05 14:57 ` Eric Schulte
2012-06-05 22:34 ` William LÉCHELLE
2012-06-06 15:19 ` henry atting
2012-06-06 19:16 ` Mikhail Titov
2012-06-06 19:25 ` Eric Schulte
2012-06-06 19:32 ` Mikhail Titov
2012-06-07 8:43 ` henry atting
2012-06-07 15:09 ` Mikhail Titov
2012-06-06 0:59 ` Mikhail Titov
2012-06-06 5:19 ` Eric Schulte
2012-06-06 17:41 ` [babel] session initialization (was RE: python/babel inline images) Mikhail Titov
2012-06-06 19:01 ` Eric Schulte
2012-06-06 19:41 ` Mikhail Titov
2012-06-06 23:06 ` Mikhail Titov
2012-06-07 22:32 ` Mikhail Titov
2012-06-07 22:44 ` Eric Schulte
2012-06-07 23:02 ` Mikhail Titov
2012-06-08 1:56 ` Mikhail Titov
2012-06-08 2:18 ` Eric Schulte
2012-06-07 22:48 ` 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=ir47gvm9bad.fsf@lycastus.phy.bnl.gov \
--to=bv@bnl.gov \
--cc=emacs-orgmode@gnu.org \
--cc=nsmp_06@online.de \
/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).