emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jarmo Hurri <jarmo.hurri@iki.fi>
To: emacs-orgmode@gnu.org
Subject: Include lines in setupfile are not evaluated: bug or feature?
Date: Sat, 07 Dec 2019 09:58:54 +0200	[thread overview]
Message-ID: <87fthwsh1d.fsf@iki.fi> (raw)


Greetings.

I am (still) trying to figure out a SINGLE common setup/include file for
all settings for a large batch of files.

I found out recently that common #properties can be set in a setup file
(but not in an included file). However, now it seems that in a setup
file I can not include all common included files. Is this intended
behaviour?

Below is an example that demonstrates this. First the main (exported
file):

# ----------------------- file main-file.org ----------------------------
#+setupfile: setup-file.org

src_elisp[:exports results :results raw]{(org-entry-get nil "MY_PROPERTY" t)}
# -----------------------------------------------------------------------

Then the setup file:

# ------------------ file setup-file.org ----------------------------
#+property: MY_PROPERTY true
#+include: setup-included.org
# -----------------------------------------------------------------------

Then the file that is supposed to be included in the setup file (and,
consequently, in the main file):

# ------------------ file setup-included.org ----------------------------
Some text to be included.
# -----------------------------------------------------------------------

But the text is not included in the main file. Documentation of
#setupfile says that

"Org parses the contents of this document as if it was included in the
buffer."

https://orgmode.org/manual/In_002dbuffer-settings.html

But that does not seem to be the case.

Jarmo

             reply	other threads:[~2019-12-07  7:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-07  7:58 Jarmo Hurri [this message]
2019-12-07 11:19 ` Include lines in setupfile are not evaluated: bug or feature? Nicolas Goaziou
2019-12-08  6:49   ` Jarmo Hurri
2019-12-08  8:38     ` Nicolas Goaziou
2019-12-16  6:17       ` Jarmo Hurri
2019-12-16 16:27         ` 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=87fthwsh1d.fsf@iki.fi \
    --to=jarmo.hurri@iki.fi \
    --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).