From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel P Gomez Subject: How to keep correct filepaths when using the #+INCLUDE derivative? Date: Wed, 28 Feb 2018 14:29:57 +0100 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48663) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1er1nz-0006r3-N1 for emacs-orgmode@gnu.org; Wed, 28 Feb 2018 08:30:00 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1er1ny-0007Zb-P1 for emacs-orgmode@gnu.org; Wed, 28 Feb 2018 08:29:59 -0500 Received: from mail-qk0-x234.google.com ([2607:f8b0:400d:c09::234]:38017) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1er1ny-0007ZM-Jg for emacs-orgmode@gnu.org; Wed, 28 Feb 2018 08:29:58 -0500 Received: by mail-qk0-x234.google.com with SMTP id s198so2914309qke.5 for ; Wed, 28 Feb 2018 05:29:58 -0800 (PST) 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" To: emacs-orgmode@gnu.org Dear org users, If I include a file child.org in parent.org using the #+INCLUDE derivative, and the following two conditions are true: 1. child.org and parent.org are not in the same directory nor share directory structure, 2. child.org contains file links with relative file paths, then exporting parent.org will produce a file with broken links. Is there a way to have org sort this out? Or even make this optional, say by using: #+INCLUDE: child.org :fix-paths t I guess the quickest (but perhaps not cleanest) way to have this feature would be to convert relative paths in file links into absolute paths within `org-export-expand-include-keyword`. I'm not that well versed in Elisp yet to do this yet, though. Are there any known solutions to this, or suggestions on how to get it working? Thanks in advance, Daniel