emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Dan Drake <dan.drake@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: inconsistency with :eval yes in orgmode.org and gnu.org manuals for org 9.6, 9.5?
Date: Mon, 27 Feb 2023 17:05:32 +0000	[thread overview]
Message-ID: <878rgjyr6r.fsf@localhost> (raw)
In-Reply-To: <CAKqbAeFRGDzQQQkXHKvDPtgM7NYybWgxpJj3yoRKnuD2bSwyVw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 624 bytes --]

Dan Drake <dan.drake@gmail.com> writes:

> It seems like ":eval yes" was removed some time ago -- see
> https://emacs.stackexchange.com/a/3570/19526.
> Did that get re-added? It seems like it was replaced by the
> org-confirm-babel-evaluate mechanism --
> https://www.gnu.org/savannah-checkouts/gnu/emacs/manual/html_node/org/Code-Evaluation-Security.html.

It did not really get removed.
But its meaning indeed changed slightly, despite what the current manual

:eval yes evaluates the code blocks, but not unconditionally. It still
obeys org-confirm-babel-evaluate.

Does the attached patch clarify the situation?

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-org-manual-Clarify-that-eval-yes-obeys-org-confirm-b.patch --]
[-- Type: text/x-patch, Size: 1054 bytes --]

From 3867672d6b38b3c0ccba0b5da8e4a3adb7f111b1 Mon Sep 17 00:00:00 2001
Message-Id: <3867672d6b38b3c0ccba0b5da8e4a3adb7f111b1.1677517512.git.yantar92@posteo.net>
From: Ihor Radchenko <yantar92@posteo.net>
Date: Mon, 27 Feb 2023 20:02:50 +0300
Subject: [PATCH] org-manual: Clarify that :eval yes obeys

* doc/org-manual.org (Limit code block evaluation): Clarify :eval yes

Reported-by: Dan Drake <dan.drake@gmail.com>
Link: https://orgmode.org/list/CAKqbAeFRGDzQQQkXHKvDPtgM7NYybWgxpJj3yoRKnuD2bSwyVw@mail.gmail.com
 doc/org-manual.org | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc/org-manual.org b/doc/org-manual.org
index 6a625b42a..1c97d6aa8 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -18123,7 +18123,8 @@ *** Limit code block evaluation
 - =yes= ::
-  Org always evaluates the source code without asking permission.
+  Org evaluates the source code, possibly asking permission according
+  to ~org-confirm-babel-evaluate~.
 - =never= or =no= ::

[-- Attachment #3: Type: text/plain, Size: 224 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>

  reply	other threads:[~2023-02-27 17:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-26 14:19 inconsistency with :eval yes in orgmode.org and gnu.org manuals for org 9.6, 9.5? Dan Drake
2023-02-27 17:05 ` Ihor Radchenko [this message]
2023-02-28 10:38   ` 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:

  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=878rgjyr6r.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=dan.drake@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).