emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Dan Drake <dan.drake@gmail.com>
To: emacs-orgmode@gnu.org
Subject: inconsistency with :eval yes in orgmode.org and gnu.org manuals for org 9.6, 9.5?
Date: Sun, 26 Feb 2023 08:19:47 -0600	[thread overview]
Message-ID: <CAKqbAeFRGDzQQQkXHKvDPtgM7NYybWgxpJj3yoRKnuD2bSwyVw@mail.gmail.com> (raw)

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

The online manuals for 16.5 Evaluating Code Blocks seem inconsistent and
include a header argument that seems to no longer be respected.

https://orgmode.org/manual/Evaluating-Code-Blocks.html, for version 9.6,
right now says you can specify a header argument ":eval yes" on source code
blocks to bypass confirmation.

However, neither
mention that. They are both for version 9.5.

It seems like ":eval yes" was removed some time ago -- see

Did that get re-added? It seems like it was replaced by the
org-confirm-babel-evaluate mechanism --

Just curious/confused. Thanks!


Ceci n'est pas une .signature.

[-- Attachment #2: Type: text/html, Size: 1750 bytes --]

             reply	other threads:[~2023-02-26 14:20 UTC|newest]

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