From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mikhail Titov Subject: [babel] #+INCLUDE does not account for relative paths to images Date: Mon, 27 Aug 2012 14:57:48 -0500 Message-ID: <9q0lih0151f.fsf@gmx.us> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([208.118.235.92]:39518) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T65Rz-0000qZ-LU for emacs-orgmode@gnu.org; Mon, 27 Aug 2012 15:58:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T65Ry-0001TE-Qd for emacs-orgmode@gnu.org; Mon, 27 Aug 2012 15:58:19 -0400 Received: from mailout-us.gmx.com ([74.208.5.67]:50154) by eggs.gnu.org with smtp (Exim 4.71) (envelope-from ) id 1T65Ry-0001T6-J4 for emacs-orgmode@gnu.org; Mon, 27 Aug 2012 15:58:18 -0400 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: emacs-orgmode@gnu.org 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