Re: [PATCH] Put reasons to stop exporting blocks at the beginning of the sentence.

2026-02-15 Thread Ihor Radchenko 
Pedro Andres Aranda Gutierrez  writes:

> Another attempt,

Applied, onto main, with minor amendments to the commit message.
I changed the message to start from capital letter and end with ".".
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=7f0e6729b

-- 
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at .
Support Org development at ,
or support my work at

Re: [PATCH] Put reasons to stop exporting blocks at the beginning of the sentence.

2026-02-09 Thread Pedro Andres Aranda Gutierrez 
Another attempt,

/PA

On Thu, 5 Feb 2026 at 17:59, Pedro Andres Aranda Gutierrez <
[email protected]> wrote:

> HI again,
>
> maybe a more "drastic" rework does a better job...
>
> /PA
>
> On Thu, 5 Feb 2026 at 16:56, Jacob S. Gordon 
> wrote:
>
>> On 2026-02-05 04:49, Pedro Andres Aranda Gutierrez wrote:
>> > The important part is the reason why you stop exporting code blocks,
>> > so put it at the beginning of the sentence
>>
>> +1
>>
>> IMO the second sentence could be improved (missing word, some may be
>> not be remembering this fact):
>>
>>   For greater security, [you can prevent] Org from evaluating code
>>   blocks [by] setting the ~org-export-use-babel~ variable to ~nil~[,
>>   but note that] header arguments will have no effect in this case.
>>
>> Thanks,
>>
>> --
>> Jacob S. Gordon
>> [email protected]
>> Please don’t send me HTML emails or MS Office/Apple iWork documents.
>> https://useplaintext.email/#etiquette
>> https://www.fsf.org/campaigns/opendocument
>>
>
>
> --
> 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
>
>

-- 
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 fe490a39d8a72ffa566a1b2d46b5e9b4364b930c Mon Sep 17 00:00:00 2001
From: "Pedro A. Aranda" 
Date: Thu, 9 Feb 2026 17:56:03 +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 | 12 +++-
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/doc/org-manual.org b/doc/org-manual.org
index 818bf0b59..5f085781c 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -19564,11 +19564,14 @@ 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.
+You can prevent Org from evaluating code blocks for speed or security
+reasons:
+
+- To speed up export, use the header argument =:eval never-export=
+  (see [[*Evaluating Code Blocks]]).
+- For greater security, set the ~org-export-use-babel~ variable to
+  ~nil~, but understand 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=.

Re: [PATCH] Put reasons to stop exporting blocks at the beginning of the sentence

2026-02-07 Thread Ihor Radchenko 
"Jacob S. Gordon"  writes:

> On 2026-02-05 11:59, Pedro Andres Aranda Gutierrez wrote:
>> maybe a more "drastic" rework does a better job...
>
> Could be! (I’ve attached your last email since the list wasn’t CC’d).
> Maybe it can be generalized, e.g.
>
>   For speed and/or security, you can prevent Org from evaluating blocks
>   at a local or global level:
>
>   - local :: use the header argument =:eval never-export= (see
> [[*Evaluating Code Blocks]]),
>
>   - global :: set the variable ~org-export-use-babel~ to ~nil~, but note
> that header arguments will have no effect in this case.

I am open to such improvements. Do you mind preparing a patch?

-- 
Ihor Radchenko // yantar92,
Org mode maintainer,
Learn more about Org mode at .
Support Org development at ,
or support my work at

Re: [PATCH] Put reasons to stop exporting blocks at the beginning of the sentence

2026-02-05 Thread Pedro Andres Aranda Gutierrez 
 Could live with that version too…
Enviado desde mi iPhone

> El 5 feb 2026, a las 21:56, Jacob S. Gordon  
> escribió:
> 
> On 2026-02-05 11:59, Pedro Andres Aranda Gutierrez wrote:
>> maybe a more "drastic" rework does a better job...
> 
> Could be! (I’ve attached your last email since the list wasn’t CC’d).
> Maybe it can be generalized, e.g.
> 
>  For speed and/or security, you can prevent Org from evaluating blocks
>  at a local or global level:
> 
>  - local :: use the header argument =:eval never-export= (see
>[[*Evaluating Code Blocks]]),
> 
>  - global :: set the variable ~org-export-use-babel~ to ~nil~, but note
>that header arguments will have no effect in this case.
> 
> --
> Jacob S. Gordon
> [email protected]
> Please don’t send me HTML emails or MS Office/Apple iWork documents.
> https://useplaintext.email/#etiquette
> https://www.fsf.org/campaigns/opendocument
>  sentence.>

Re: [PATCH] Put reasons to stop exporting blocks at the beginning of the sentence

2026-02-05 Thread Jacob S. Gordon 
On 2026-02-05 11:59, Pedro Andres Aranda Gutierrez wrote:
> maybe a more "drastic" rework does a better job...

Could be! (I’ve attached your last email since the list wasn’t CC’d).
Maybe it can be generalized, e.g.

  For speed and/or security, you can prevent Org from evaluating blocks
  at a local or global level:

  - local :: use the header argument =:eval never-export= (see
[[*Evaluating Code Blocks]]),
   
  - global :: set the variable ~org-export-use-babel~ to ~nil~, but note
that header arguments will have no effect in this case.

-- 
Jacob S. Gordon
[email protected]
Please don’t send me HTML emails or MS Office/Apple iWork documents.
https://useplaintext.email/#etiquette
https://www.fsf.org/campaigns/opendocument--- Begin Message ---
HI again,

maybe a more "drastic" rework does a better job...

/PA

On Thu, 5 Feb 2026 at 16:56, Jacob S. Gordon 
wrote:

> On 2026-02-05 04:49, Pedro Andres Aranda Gutierrez wrote:
> > The important part is the reason why you stop exporting code blocks,
> > so put it at the beginning of the sentence
>
> +1
>
> IMO the second sentence could be improved (missing word, some may be
> not be remembering this fact):
>
>   For greater security, [you can prevent] Org from evaluating code
>   blocks [by] setting the ~org-export-use-babel~ variable to ~nil~[,
>   but note that] header arguments will have no effect in this case.
>
> Thanks,
>
> --
> Jacob S. Gordon
> [email protected]
> Please don’t send me HTML emails or MS Office/Apple iWork documents.
> https://useplaintext.email/#etiquette
> https://www.fsf.org/campaigns/opendocument
>


-- 
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 fe490a39d8a72ffa566a1b2d46b5e9b4364b930c Mon Sep 17 00:00:00 2001
From: "Pedro A. Aranda" 
Date: Thu, 5 Feb 2026 17:56:03 +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 | 12 +++-
 1 file changed, 7 insertions(+), 5 deletions(-)

diff --git a/doc/org-manual.org b/doc/org-manual.org
index d89235141..792105b11 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -19549,11 +19549,13 @@ 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.
+You can prevent Org from evaluating code blocks for different reasons
+and using different approaches:
+1) To speed up export, use the header argument =:eval never-export=
+   (see [[*Evaluating Code Blocks]]).
+2) For greater security, set the ~org-export-use-babel~ variable
+   to ~nil~; but note 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

--- End Message ---

Re: [PATCH] Put reasons to stop exporting blocks at the beginning of the sentence.

2026-02-05 Thread Jacob S. Gordon 
On 2026-02-05 04:49, Pedro Andres Aranda Gutierrez wrote:
> The important part is the reason why you stop exporting code blocks,
> so put it at the beginning of the sentence

+1

IMO the second sentence could be improved (missing word, some may be
not be remembering this fact):

  For greater security, [you can prevent] Org from evaluating code
  blocks [by] setting the ~org-export-use-babel~ variable to ~nil~[,
  but note that] header arguments will have no effect in this case.

Thanks,

-- 
Jacob S. Gordon
[email protected]
Please don’t send me HTML emails or MS Office/Apple iWork documents.
https://useplaintext.email/#etiquette
https://www.fsf.org/campaigns/opendocument