emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: Stefan Vollmar <vollmar@nf.mpg.de>
Cc: emacs-orgmode Mode <emacs-orgmode@gnu.org>
Subject: Re: Inconsistent behaviour when #+setupfile is used recursively
Date: Mon, 25 Jul 2011 15:46:53 +0200	[thread overview]
Message-ID: <87zkk2xyk2.fsf@gnu.org> (raw)
In-Reply-To: <FAF26A12-A952-4C57-9A34-59D05452F254@nf.mpg.de> (Stefan Vollmar's message of "Wed, 13 Jul 2011 09:49:09 +0200")

Hi Stefan,

Stefan Vollmar <vollmar@nf.mpg.de> writes:

> 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. 

This is fixed in latest git.  Thanks for signaling this bug.



      reply	other threads:[~2011-07-25 13:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-13  7:49 Inconsistent behaviour when #+setupfile is used recursively Stefan Vollmar
2011-07-25 13:46 ` Bastien [this message]

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:

  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=87zkk2xyk2.fsf@gnu.org \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=vollmar@nf.mpg.de \


* 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


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).