From: Richard Hansen <rhansen@bbn.com>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH v3] fix SETUPFILE pathname expansion with subdirectories
Date: Thu, 24 Sep 2015 17:55:14 -0400 [thread overview]
Message-ID: <56047142.1060404@bbn.com> (raw)
In-Reply-To: <87mvwcw7jq.fsf@nicolasgoaziou.fr>
On 2015-09-24 04:22, Nicolas Goaziou wrote:
> Applied. Thank you.
Thank you!
>
> Would it make sense to do the same for INCLUDE? If so, would you want to
> have a look at it?
A chain of #+INCLUDEs already works OK. I'll send a patch that tweaks
the test-org-export/expand-include test case to ensure that it continues
to work.
The intended meanings of #+INCLUDE and #+SETUPFILE have never been clear
to me, so I have a couple of questions:
* What is supposed to happen if you have a #+SETUPFILE that has
an #+INCLUDE?
* What is supposed to happen if you have an #+INCLUDE file that
has a #+SETUPFILE line?
-Richard
next prev parent reply other threads:[~2015-09-24 21:55 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 [this message]
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
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56047142.1060404@bbn.com \
--to=rhansen@bbn.com \
--cc=emacs-orgmode@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).