From: Mikhail Titov <mlt@gmx.us>
To: emacs-orgmode@gnu.org
Subject: [babel] #+INCLUDE does not account for relative paths to images
Date: Mon, 27 Aug 2012 14:57:48 -0500 [thread overview]
Message-ID: <9q0lih0151f.fsf@gmx.us> (raw)
I've noticed that if I include one Org file into another using
#+INCLUDE, then I'm not getting a proper path to babel-generated figures
at least while doing HTML export. I believe it is still an issue for
non-babel images.
I feel like it would be nice to export an updated relative path to
included image file with a different base when exporting master
document. Current implementation forces either to keep project Org files
in the same folder or use more sophisticated relative paths like
../sibling-project/foo.png . Though I did not try the latter.
--
Mikhail
next reply other threads:[~2012-08-27 19:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-27 19:57 Mikhail Titov [this message]
2012-09-27 9:21 ` [babel] #+INCLUDE does not account for relative paths to images Bastien
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=9q0lih0151f.fsf@gmx.us \
--to=mlt@gmx.us \
--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).