From: Ihor Radchenko <yantar92@posteo.net>
To: Bruno BEAUFILS <bruno.beaufils@univ-lille.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: code block not evaluated during export when placed in SETUPFILE [9.4 (9.4-elpa @ /home/bruno/.emacs.d/elpa/org-9.4/)]
Date: Sat, 18 Feb 2023 10:32:38 +0000 [thread overview]
Message-ID: <87mt5bl0vt.fsf@localhost> (raw)
In-Reply-To: <20230216235224.7g5xdlkcnw2z4k3n@settat>
[-- Attachment #1: Type: text/plain, Size: 600 bytes --]
Bruno BEAUFILS <bruno.beaufils@univ-lille.fr> writes:
> In the org manual the following lines can be read about #+SETUPFILE:
> (emphaze is mine):
>
> » Org also parses and loads the document during normal exporting process.
> » Org parses the contents of this document **as if it was included** in the
> » buffer. It can be **another Org file**.
#+SETUPFILE is only parsed for export settings. It is not actually
included. I admit that the wording may be confusing.
To actually include the document, use #+INCLUDE.
I tried to clarify the manual section in the attached patch.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-org-manual.org-Clarify-what-SETUPFILE-does.patch --]
[-- Type: text/x-patch, Size: 2259 bytes --]
From 64cc230e39378d7c1fee4954f415358ae8055c4f Mon Sep 17 00:00:00 2001
Message-Id: <64cc230e39378d7c1fee4954f415358ae8055c4f.1676716311.git.yantar92@posteo.net>
From: Ihor Radchenko <yantar92@posteo.net>
Date: Sat, 18 Feb 2023 13:30:39 +0300
Subject: [PATCH] org-manual.org: Clarify what SETUPFILE does
* doc/org-manual.org (Summary of In-Buffer Settings): Clarify that
only in-buffer settings are considered in SETUPFILE. Other contents
is ignored. Split the explanation into multiple paragraphs.
Reported-by: Bruno BEAUFILS <bruno.beaufils@univ-lille.fr>
Link: https://orgmode.org/list/20230216235224.7g5xdlkcnw2z4k3n@settat
---
doc/org-manual.org | 19 +++++++++++--------
1 file changed, 11 insertions(+), 8 deletions(-)
diff --git a/doc/org-manual.org b/doc/org-manual.org
index 5b6633417..60c062921 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -19922,15 +19922,18 @@ ** Summary of In-Buffer Settings
#+cindex: @samp{SETUPFILE}, keyword
The setup file or a URL pointing to such file is for additional
in-buffer settings. Org loads this file and parses it for any
- settings in it only when Org opens the main file. If URL is
+ settings in it when Org opens the main file. If URL is
specified, the contents are downloaded and stored in a temporary
- file cache. {{{kbd(C-c C-c)}}} on the settings line parses and
- loads the file, and also resets the temporary file cache. Org also
- parses and loads the document during normal exporting process. Org
- parses the contents of this document as if it was included in the
- buffer. It can be another Org file. To visit the file---not
- a URL---use {{{kbd(C-c ')}}} while point is on the line with the
- file name.
+ file cache. {{{kbd(C-c C-c)}}} on the settings line re-parses and
+ re-loads the file, and also resets the temporary file cache.
+
+ Org also parses and loads /in-buffer settings/ from the setup file
+ during normal exporting process. Org parses the /in-buffer
+ settings/ as if it was included in the containing Org buffer. The
+ rest of the contents of setup file is ignored.
+
+ To visit the setup file---not a URL---use {{{kbd(C-c ')}}} while point
+ is on the line with the setup file name.
- =#+STARTUP:= ::
--
2.39.1
[-- Attachment #3: Type: text/plain, Size: 225 bytes --]
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-02-18 10:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 23:52 Bug: code block not evaluated during export when placed in SETUPFILE [9.4 (9.4-elpa @ /home/bruno/.emacs.d/elpa/org-9.4/)] Bruno BEAUFILS
2023-02-18 10:32 ` Ihor Radchenko [this message]
2023-02-18 14:00 ` Bruno BEAUFILS
2023-04-02 13:58 ` Ihor Radchenko
2023-04-03 7:10 ` Bruno BEAUFILS
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=87mt5bl0vt.fsf@localhost \
--to=yantar92@posteo.net \
--cc=bruno.beaufils@univ-lille.fr \
--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).