From: Stefan Vollmar <vollmar@nf.mpg.de>
To: emacs-orgmode Mode <emacs-orgmode@gnu.org>
Subject: Inconsistent behaviour when #+setupfile is used recursively
Date: Wed, 13 Jul 2011 09:49:09 +0200 [thread overview]
Message-ID: <FAF26A12-A952-4C57-9A34-59D05452F254@nf.mpg.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1617 bytes --]
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: vollmar@nf.mpg.de http://www.nf.mpg.de
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 4409 bytes --]
next reply other threads:[~2011-07-13 7:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 7:49 Stefan Vollmar [this message]
2011-07-25 13:46 ` Inconsistent behaviour when #+setupfile is used recursively Bastien
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=FAF26A12-A952-4C57-9A34-59D05452F254@nf.mpg.de \
--to=vollmar@nf.mpg.de \
--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).