Hello,
Richard Hansen writes:
> The intended meanings of #+INCLUDE and #+SETUPFILE have never been clear
> to me, so I have a couple of questions:
INCLUDE is only expanded during export. SETUPFILE are parsed when
refreshing document properties (e.g., when using C-c C-c on a keyword).
> * Wha
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 e
Hello,
Richard Hansen writes:
> Any other feedback on this patch?
Apparently, no. Applied. Thank you.
Would it make sense to do the same for INCLUDE? If so, would you want to
have a look at it?
Regards,
--
Nicolas Goaziou
Any other feedback on this patch?
Thanks,
Richard
On 2015-09-20 01:28, Richard Hansen wrote:
> * lisp/org-macro.el (org-macro--collect-macros): cd to the directory
> containing the SETUPFILE before recursing so that relative pathnames
> in the SETUPFILE are expanded properly.
>
> * lisp/org.el
* lisp/org-macro.el (org-macro--collect-macros): cd to the directory
containing the SETUPFILE before recursing so that relative pathnames
in the SETUPFILE are expanded properly.
* lisp/org.el (org--setup-collect-keywords): cd to the directory
containing the SETUPFILE before recursing so that relat