From: Bruno BEAUFILS <bruno.beaufils@univ-lille.fr>
To: emacs-orgmode@gnu.org
Cc: Bruno BEAUFILS <bruno.beaufils@univ-lille.fr>
Subject: 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: Fri, 17 Feb 2023 00:52:24 +0100 [thread overview]
Message-ID: <20230216235224.7g5xdlkcnw2z4k3n@settat> (raw)
[-- 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 --]
next reply other threads:[~2023-02-18 5:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 23:52 Bruno BEAUFILS [this message]
2023-02-18 10:32 ` Bug: code block not evaluated during export when placed in SETUPFILE [9.4 (9.4-elpa @ /home/bruno/.emacs.d/elpa/org-9.4/)] Ihor Radchenko
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=20230216235224.7g5xdlkcnw2z4k3n@settat \
--to=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).