From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Emacs Org mode mailing list <emacs-orgmode@gnu.org>
Subject: processing of babel blocks and select_tags
Date: Fri, 18 Feb 2022 11:57:19 +0000 [thread overview]
Message-ID: <87wnhss7z4.fsf@ucl.ac.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1171 bytes --]
Hello all,
TL;DR: can I have org completely ignore src blocks in non-selected
sections during export without using COMMENT?
Longer version: I am in the process of writing a book. I prefer to have
all the content in one file and use SELECT_TAGS to limit the export (for
formatting) to the current section I am working on.
I have noticed that all org babel src blocks are processed in some way
even if (a) they are not in a selected section and (b) have, for
instance, ":eval no-export" set. For some of these blocks, the
processing time appears to be quite significant, e.g. if they have a
":var x=somebigtable", but I could be wrong about this, of course.
I do not understand why these src blocks are processed at all. Is there
some way to stop them being processed? I know I could "comment" out all
other sections but that's a lot more work and messy than simply tagging
the current section to be selected.
Attached is a minimal example. When I export, I see these messages:
org-babel-exp process julia at position 162...
org-babel-exp process julia at position 384...
Thank you,
eric
--
: Eric S Fraga, with org release_9.5.2-385-g37d8bc in Emacs 29.0.50
[-- Attachment #2: tag.org --]
[-- Type: application/vnd.lotus-organizer, Size: 461 bytes --]
next reply other threads:[~2022-02-18 12:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-18 11:57 Eric S Fraga [this message]
2022-02-18 15:33 ` processing of babel blocks and select_tags John Kitchin
2022-02-18 15:45 ` Eric S Fraga
2022-02-19 7:54 ` Jeremie Juste
2022-02-19 16:47 ` Eric S Fraga
2022-10-23 5:35 ` Ihor Radchenko
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=87wnhss7z4.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--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).