From: John Kitchin <jkitchin@andrew.cmu.edu>
To: emacs-orgmode@gnu.org
Subject: Re: Emacs-orgmode Digest, Vol 89, Issue 30
Date: Wed, 24 Jul 2013 12:55:30 -0400 [thread overview]
Message-ID: <CAJ51ETpe5s-2zzFJnsJXTmzkTO15S6LNePu_Lya7UnA2Q7kxTA@mail.gmail.com> (raw)
In-Reply-To: <mailman.120.1374681631.3997.emacs-orgmode@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2306 bytes --]
> ---------- Forwarded message ----------
> From: Nick Dokos <ndokos@gmail.com>
> To: emacs-orgmode@gnu.org
> Cc:
> Date: Wed, 24 Jul 2013 04:50:36 -0400
> Subject: Re: [O] links to files in a zip archive and inline images in zip
> archive
> John Kitchin <jkitchin@andrew.cmu.edu> writes:
>
> > I am trying to make an org-mode zip archive. The idea is basically to
> > zip up the org-file, and the images it might refer to. What I would
> > really like is to be able to open the zip-file in emacs, and have the
> > images shown inline like they are when the archive is expanded.
> >
> > I had no problem making the zip archive, and it opens fine in emacs. I
> > can read the org file fine, but there are no inline images, and the
> > links to the images do not work.
> >
> > It might be ok if the links in the org-file would open the images, but
> > they do not do that either (I get cannot display image: cannot
> > determine image type and a blank screen).
> >
> > Is this idea way off base? or is there a way to get it to work? I do
> > not have to stick with zip archives if another format would work well.
> >
> My guess is that your links use absolute paths. I had no problem doing
> this with a file using relative paths and the following directory
> structure:
>
> tmp -- kitchin.org
> `- images -- foo.png
>
> kitchin.org looks like this:
>
> --8<---------------cut here---------------start------------->8---
> #+STARTUP: inlineimages
>
> * foo
>
> This [[file:images/foo.png]] is an inline image.
> --8<---------------cut here---------------end--------------->8---
>
> and I zipped like this:
>
> $ zip kitchin.zip kitchin.org images
>
> I can then open the zip file, and open kitchin.org inside the zip file
> with the inline image showing.
> --
> Nick
>
>
This works if the unzipped directory images exists. In my case that won't
be true.
What I am doing is creating a script that runs a python script, captures
any images created by matplotlib, creates an org-file, then creates a
zip-file that contains the org-file of the script, the output, and links to
the figures, as well as the figures. The zip-file will then be submitted to
a server, where the original images do not exist. I can unzip the zip-file
on the server, and it works fine, but I was trying to avoid that.
j
[-- Attachment #2: Type: text/html, Size: 3108 bytes --]
next parent reply other threads:[~2013-07-24 16:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.120.1374681631.3997.emacs-orgmode@gnu.org>
2013-07-24 16:55 ` John Kitchin [this message]
2013-07-24 18:26 ` Emacs-orgmode Digest, Vol 89, Issue 30 Nick Dokos
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=CAJ51ETpe5s-2zzFJnsJXTmzkTO15S6LNePu_Lya7UnA2Q7kxTA@mail.gmail.com \
--to=jkitchin@andrew.cmu.edu \
--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
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).