From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Richard Hansen <rhansen@bbn.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH 2/2] fix SETUPFILE pathname expansion from within an INCLUDE
Date: Fri, 25 Sep 2015 13:58:08 +0200 [thread overview]
Message-ID: <87si62d833.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <1443133241-501-2-git-send-email-rhansen@bbn.com> (Richard Hansen's message of "Thu, 24 Sep 2015 18:20:41 -0400")
Hello,
Richard Hansen <rhansen@bbn.com> writes:
> * lisp/ox.el (defun org-export-expand-include-keyword): cd instead of
> passing DIR to expand-file-name so that if the INCLUDE file has a
> SETUPFILE line with a relative pathname the full pathname to the
> SETUPFILE will be expanded properly.
SETUPFILE within INCLUDE doesn't do what you think.
Org first includes contents from all INCLUDE keyword, then reads read
SETUPFILE keywords.
>
> Assume the following files:
>
> /home/foo/a.org:
> #+INCLUDE: subdir/b.org
>
> /home/foo/subdir/b.org:
> #+SETUPFILE: c.org
>
> /home/foo/subdir/c.org:
> stuff
In your example, a.org becomes
#+SETUPFILE: c.org
So, it is meant to look after /home/foo/c.org.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2015-09-25 11:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-19 0:22 [PATCH] fix SETUPFILE pathname expansion with subdirectories Richard Hansen
2015-09-19 8:16 ` Nicolas Goaziou
2015-09-19 20:18 ` Richard Hansen
2015-09-19 22:07 ` [PATCH v2] " Richard Hansen
2015-09-19 22:43 ` Kyle Meyer
2015-09-19 23:14 ` Richard Hansen
2015-09-20 5:07 ` Kyle Meyer
2015-09-20 5:28 ` [PATCH v3] " Richard Hansen
2015-09-22 22:28 ` Richard Hansen
2015-09-24 8:22 ` Nicolas Goaziou
2015-09-24 21:55 ` Richard Hansen
2015-09-24 22:20 ` [PATCH 1/2] test INCLUDE " Richard Hansen
2015-09-24 22:20 ` [PATCH 2/2] fix SETUPFILE pathname expansion from within an INCLUDE Richard Hansen
2015-09-25 11:58 ` Nicolas Goaziou [this message]
2015-09-25 11:51 ` [PATCH v3] fix SETUPFILE pathname expansion with subdirectories Nicolas Goaziou
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87si62d833.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=rhansen@bbn.com \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.