From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert Goldman Subject: Re: Images in included files Date: Sun, 01 May 2011 17:37:18 -0500 Message-ID: <4DBDE09E.2010000@sift.info> References: <81lizlt0ue.fsf@gmail.com> <001636c5adbf92be9b04a067446e@google.com> Reply-To: rpgoldman@sift.info Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([140.186.70.92]:58500) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QGfGT-0003hm-L8 for emacs-orgmode@gnu.org; Sun, 01 May 2011 18:37:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QGfGS-0000Ks-MF for emacs-orgmode@gnu.org; Sun, 01 May 2011 18:37:21 -0400 Received: from mpls.sift.info ([75.146.46.193]:35298) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QGfGS-0000Ko-IL for emacs-orgmode@gnu.org; Sun, 01 May 2011 18:37:20 -0400 In-Reply-To: <001636c5adbf92be9b04a067446e@google.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Org Mode I'm having exactly this same problem. I have a file, suggestions.org, in directory ~/x/y/z/top/child/ that contains many images. These are included by means of links such as [[./foo.pdf]] Now, I have a parent file in top/, manual.org, and I want to #+include "child/suggestions.org" Unfortunately, this breaks all the figure links in suggestions.org, because "." is interpreted as top/ and not top/child/. Even more unfortunately, this is a shared document, and a number of people are going to check it out from a source code repository (subversion in this case). This means that I cannot specify the images as ~/x/y/z/top/child/foo.pdf because I cannot force my co-authors to check out the top/ to ~/x/y/z. Indeed, I cannot even force my co-authors to have directories x/ x/y or x/y/z... So what is needed, I believe is some way of indicating that these relative links should be resolved at *include* time, rather than later. I am pretty sure that this is the same problem John Tait alludes to, with some more details. Best, Robert