From: Jarmo Hurri <jarmo.hurri@iki.fi>
To: emacs-orgmode@gnu.org
Subject: Re: Include lines in setupfile are not evaluated: bug or feature?
Date: Sun, 08 Dec 2019 08:49:21 +0200 [thread overview]
Message-ID: <87a7831fda.fsf@iki.fi> (raw)
In-Reply-To: 8736dwwfgg.fsf@nicolasgoaziou.fr
Hello Nicolas!
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> SETUPFILE and INCLUDE are orthogonal. There is no point in mixing
> them.
Ok. As a programmer I was hoping to mix them, because it would be
logical to have _one_ header file that defines all the common things for
a set of related files.
But perhaps I can get away with using SETUPFILEs only. I will see.
> Jarmo Hurri <jarmo.hurri@iki.fi> writes:
>> 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.
>
> SETUPFILE keyword recursively loads configuration from other files,
> without inserting anything. INCLUDE keyword recursively inserts
> contents from other files in the current document, but there is no
> guarantee that configuration from these files will be inherited.
Do I understand correctly: the description in the documentation is not
correct in the sense that not all contents from SETUPFILE is evaluated
as if it were included in the buffer?
I am just trying to think about how this limitation, if it exists,
should be expressed in documentation. Shall I give it a try?
Thanks for the clarifying response!
Jarmo
next prev parent reply other threads:[~2019-12-08 6:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-07 7:58 Include lines in setupfile are not evaluated: bug or feature? Jarmo Hurri
2019-12-07 11:19 ` Nicolas Goaziou
2019-12-08 6:49 ` Jarmo Hurri [this message]
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=87a7831fda.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).