* Bug: code block not evaluated during export when placed in SETUPFILE [9.4 (9.4-elpa @ /home/bruno/.emacs.d/elpa/org-9.4/)]
@ 2023-02-16 23:52 Bruno BEAUFILS
2023-02-18 10:32 ` Ihor Radchenko
0 siblings, 1 reply; 5+ messages in thread
From: Bruno BEAUFILS @ 2023-02-16 23:52 UTC (permalink / raw)
To: emacs-orgmode; +Cc: Bruno BEAUFILS
[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]
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**.
However, when I consider the two following files, code block in
setup.org is not evaluated at all when exporting, whereas when
#+SETUPFILE: is replaced by #+INCLUDE: it is.
--- main.org ----------------------------------------------------------
#+setupfile: setup.org
Something
------------------------------------------------------------------------
--- setup.org ---------------------------------------------------------
#+begin_src emacs-lisp :exports results :result silent
(message "DEBUG")
#+end_src
------------------------------------------------------------------------
Emacs : GNU Emacs 27.1 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.24, cairo version 1.16.0)
of 2021-03-28, modified by Debian
Package: Org mode version 9.4 (9.4-elpa @ /home/bruno/.emacs.d/elpa/org-9.4/)
--
Bruno BEAUFILS
Trésorier de la Societé Informatique de France
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* 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/)]
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
2023-02-18 14:00 ` Bruno BEAUFILS
2023-04-02 13:58 ` Ihor Radchenko
0 siblings, 2 replies; 5+ messages in thread
From: Ihor Radchenko @ 2023-02-18 10:32 UTC (permalink / raw)
To: Bruno BEAUFILS; +Cc: emacs-orgmode
[-- 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>
^ permalink raw reply related [flat|nested] 5+ messages in thread* 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/)]
2023-02-18 10:32 ` Ihor Radchenko
@ 2023-02-18 14:00 ` Bruno BEAUFILS
2023-04-02 13:58 ` Ihor Radchenko
1 sibling, 0 replies; 5+ messages in thread
From: Bruno BEAUFILS @ 2023-02-18 14:00 UTC (permalink / raw)
To: Ihor Radchenko; +Cc: Bruno BEAUFILS, emacs-orgmode
[-- Attachment #1: Type: text/plain, Size: 228 bytes --]
On Sat, Feb 18, 2023 at 10:32:38AM +0000, Ihor Radchenko wrote:
> I tried to clarify the manual section in the attached patch.
Thank's for your work.
--
Bruno BEAUFILS
Trésorier de la Societé Informatique de France
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* 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/)]
2023-02-18 10:32 ` Ihor Radchenko
2023-02-18 14:00 ` Bruno BEAUFILS
@ 2023-04-02 13:58 ` Ihor Radchenko
2023-04-03 7:10 ` Bruno BEAUFILS
1 sibling, 1 reply; 5+ messages in thread
From: Ihor Radchenko @ 2023-04-02 13:58 UTC (permalink / raw)
To: Bruno BEAUFILS; +Cc: emacs-orgmode
Ihor Radchenko <yantar92@posteo.net> writes:
> #+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.
Applied, onto main.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=15e70240e
Fixed.
--
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>
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2023-04-03 7:32 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2023-02-18 14:00 ` Bruno BEAUFILS
2023-04-02 13:58 ` Ihor Radchenko
2023-04-03 7:10 ` Bruno BEAUFILS
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).