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

From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: emacs-orgmode@gnu.org
Subject: Re: How to fix path to figures in included files
Date: Thu, 20 Oct 2016 18:49:26 +0200	[thread overview]
Message-ID: <878ttjynhl.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <871szlzfz0.fsf@thinkpad.rath.org> (Nikolaus Rath's message of "Wed, 12 Oct 2016 09:31:31 -0700")

Hello,

Nikolaus Rath <Nikolaus@rath.org> writes:

> When using INCLUDE in an org-file to include a file in a sub-directory
> (e.g. "#+INCLUDE: preamble/preamble.org"), and the included file in turn
> refers to a file ("[[./figure1.png]]"), then the LaTeX export for the
> top-level org file refers to the file with its path relative to the
> included .org file rather than the top-level org file for which LaTeX is
> generated.
>
> Is there a way to fix this?

I'm pretty sure that question was raised before on this ML, but, after
a cursory look, I cannot find any reference to it.

There is no way to fix this for the time being. I can think of two
solutions.

1. We could add a hook just before inserting included file in the master
   document, so you get a chance to rewrite links yourself.

2. We could do that rewriting every file link with a relative path
   ourselves.

Second option only makes sense if the behavior you suggest is always the
one needed. We may need some more feedback about this.

Also, it could fail for some link types, when the path is not obviously
a file, e.g. [[foo:a/b]]. IOW, if implemented, we would have to limit
ourselves to "file:" links.

OTOH, the first solution is easy to implement.

Regards,

-- 
Nicolas Goaziou

     prev parent reply	other threads:[~2016-10-20 16:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-12 16:31 How to fix path to figures in included files Nikolaus Rath
2016-10-20 16:49 ` Nicolas Goaziou [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=878ttjynhl.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --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).