The important part is the reason why you stop exporting code blocks, so put it at the beginning of the sentence
/PA -- Fragen sind nicht da, um beantwortet zu werden, Fragen sind da um gestellt zu werden Georg Kreisler "Sagen's Paradeiser" (ORF: Als Radiohören gefährlich war) => write BE! Year 2 of the New Koprocracy
From 3c4790c530ee4b8392f5763a58e8bbd7dd15ab2e Mon Sep 17 00:00:00 2001 From: "Pedro A. Aranda" <[email protected]> Date: Thu, 5 Feb 2026 10:43:17 +0100 Subject: [PATCH] doc/org-manual.org: Rephrase code block evaluation control doc/org-manual.org: put the reasons why one might need to stop code block evaluation at the beginning of the sentence for more clarity --- doc/org-manual.org | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/doc/org-manual.org b/doc/org-manual.org index d89235141..00c2fcc5d 100644 --- a/doc/org-manual.org +++ b/doc/org-manual.org @@ -19549,11 +19549,11 @@ Note that all the links pointing to a source block exported using unless broken links are allowed during export (see [[*Export Settings]]). #+vindex: org-export-use-babel -To stop Org from evaluating code blocks to speed up export, use the -header argument =:eval never-export= (see [[*Evaluating Code Blocks]]). -To stop Org from evaluating code blocks for greater security, set the -~org-export-use-babel~ variable to ~nil~, but understand that header -arguments will have no effect. +To speed up export, stop Org from evaluating code blocks using the +header argument =:eval never-export= (see [[*Evaluating Code +Blocks]]). For greater security, stop Org from evaluating code blocks +setting the ~org-export-use-babel~ variable to ~nil~; remember that +header arguments will have no effect in this case. If results of evaluation are not marked for export (=:exports code= or =:exports none=), Org will not evaluate them, even for =:eval yes=. -- 2.43.0
