[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[O] Inconsistent behaviour when #+setupfile is used recursively
From: |
Stefan Vollmar |
Subject: |
[O] Inconsistent behaviour when #+setupfile is used recursively |
Date: |
Wed, 13 Jul 2011 09:49:09 +0200 |
Hi,
we use Org-mode for software documentation and have come across the following
behaviour with version 7.6 (release_7.6.71.g22fa9):
our documentation is located in the directory doc/usage, e.g.
doc/usage/index.org or doc/usage/tutorial.org, whereas Org-Mode's setupfiles
are stored in doc/common/org, e.g. doc/common/org/setup-toc-large or
doc/common/org/setup-common. When we include a setupfile from
doc/usage/index.org using
#+setupfile: ../common/org/setup-toc-large
everything works fine. The path of the setupfile is relative to the path of
index.org.
However, when setup-toc-large itself includes another setupfile with
setup-common using a relative path, the path is still treated as relative to
index.org, not relative to setup-toc-large. Therefore, when using the line
#+setupfile: setup-common
within setup-toc-large, Org-Mode fails to find setup-common. When changing the
above line to
#+setupfile: ../common/org/setup-common
the documentation builds successfully.
We would expect Org-mode to search for an include file relative to the file
that contains the setupfile-statement. Maybe a simple solution would be to
temporarily set the current working dir to the path of the including file
(around line 17620 in org.el)? Many thanks in advance!
Warm regards,
Stefan
--
Dr. Stefan Vollmar, Dipl.-Phys.
Head of IT group
Max-Planck-Institut für neurologische Forschung
Gleuelerstr. 50, 50931 Köln, Germany
Tel.: +49-221-4726-213 FAX +49-221-4726-298
Tel.: +49-221-478-5713 Mobile: 0160-93874279
E-Mail: address@hidden http://www.nf.mpg.de
smime.p7s
Description: S/MIME cryptographic signature
- [O] Inconsistent behaviour when #+setupfile is used recursively,
Stefan Vollmar <=