emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: Mikhail Titov <mlt@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: [babel] #+INCLUDE does not account for relative paths to images
Date: Thu, 27 Sep 2012 11:21:13 +0200	[thread overview]
Message-ID: <87ipaz4y9i.fsf@bzg.ath.cx> (raw)
In-Reply-To: <9q0lih0151f.fsf@gmx.us> (Mikhail Titov's message of "Mon, 27 Aug 2012 14:57:48 -0500")

Hi Mikhail,

Mikhail Titov <mlt@gmx.us> writes:

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

I agree but the implementation is not straightforward. 

If you or someone else can come up with a patch for this,
I'd be happy to apply it.

Thanks,

-- 
 Bastien

      reply	other threads:[~2012-09-27  9:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-27 19:57 Mikhail Titov
2012-09-27  9:21 ` Bastien [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=87ipaz4y9i.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=mlt@gmx.us \
    /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).