From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel P Gomez Subject: Re: How to keep correct filepaths when using the #+INCLUDE derivative? Date: Wed, 28 Feb 2018 21:11:01 +0100 Message-ID: References: <87woyxhuk2.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50628) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1er847-0007Js-La for emacs-orgmode@gnu.org; Wed, 28 Feb 2018 15:11:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1er846-0006UC-Jg for emacs-orgmode@gnu.org; Wed, 28 Feb 2018 15:11:03 -0500 Received: from mail-qk0-x22a.google.com ([2607:f8b0:400d:c09::22a]:39789) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1er846-0006St-EN for emacs-orgmode@gnu.org; Wed, 28 Feb 2018 15:11:02 -0500 Received: by mail-qk0-x22a.google.com with SMTP id z197so4656546qkb.6 for ; Wed, 28 Feb 2018 12:11:02 -0800 (PST) In-Reply-To: <87woyxhuk2.fsf@nicolasgoaziou.fr> 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: Nicolas Goaziou Cc: emacs-orgmode@gnu.org Sorry for the ignorance, but where could I look up how to use a parse tree filter? And where would these modifications make sense? Any pointers towards documentation, functions, or any help of any kind would be appreciated. I must say I am a bit lost. Thank you in advance, Daniel On Wed, Feb 28, 2018 at 6:51 PM, Nicolas Goaziou wrote: > Hello, > > Daniel P Gomez writes: > >> 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? > > As you suggest, I would use a parse tree filter that turns every > relative file link into an absolute one. > > Regards, > > -- > Nicolas Goaziou