From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: per-file (or, really, per buffer) allowing/disallowing code block execution
Date: Thu, 22 Sep 2022 21:17:20 +0700 [thread overview]
Message-ID: <tghqpi$150a$1@ciao.gmane.io> (raw)
In-Reply-To: <m2illgsaz8.fsf@me.com>
On 22/09/2022 03:56, Rudolf Adamkovič wrote:
> Greg Minshall writes:
>
>> i'm a bit unclear. does your (single?) Org notebook consist of *one*
>> file (and thus, [normally? always? my ignorance precedes me], one
>> buffer), or two files (thus, two buffers).
>
> One file, two kinds of "src" blocks.
>
>> in the former case (one buffer), i don't know if these proposals will
>> help. though, maybe as they are flushed out (precedence of the
>> buffer-local and/or global-local with header line constructs), it
>> would?
>
> Interesting. Suppose I have 'org-confirm-babel-evaluate' set to 'nil'
> and I answer "no to all" during 'org-babel-execute-buffer'. I would
> expect that to mean "answer 'no' to every :eval query" block and execute
> the rest as usual. If so, that would save me from having to answer "no"
> dozen times. Good point!
Since `org-confirm-babel-evaluate' may be customized to a function,
every participant of this thread may implement their preferred policies
with no modification of Org code or even an advice to the default
function. If proven by some usage period convenient variants emerged
during such activity then they may be polished to handle corner cases
(indirect buffers, etc.) and added to Org.
However some functions will likely specific to particular users, e.g.
consider documents in some folder safe as created by the user, but
execution of code blocks from other files are suppressed because they
may be received from less trusted sources.
next prev parent reply other threads:[~2022-09-22 14:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-05 23:50 per-file (or, really, per buffer) allowing/disallowing code block execution Fedja Beader
2022-09-06 13:33 ` Ihor Radchenko
2022-09-06 19:05 ` Greg Minshall
2022-09-07 0:17 ` Steven Harris
2022-09-07 8:49 ` Greg Minshall
2022-09-08 5:53 ` Ihor Radchenko
2022-09-08 12:34 ` Fedja Beader
2022-09-08 17:41 ` tomas
2022-09-09 5:50 ` Ihor Radchenko
2022-09-10 0:19 ` Fedja Beader
2022-09-11 9:10 ` Ihor Radchenko
2022-09-12 13:56 ` Greg Minshall
2022-09-12 20:38 ` Tim Cross
2022-09-13 4:47 ` Greg Minshall
2022-09-19 18:25 ` Rudolf Adamkovič
2022-09-19 19:28 ` Greg Minshall
2022-09-21 20:56 ` Rudolf Adamkovič
2022-09-22 14:17 ` Max Nikulin [this message]
2022-09-23 2:31 ` Ihor Radchenko
2022-09-19 9:23 ` Fraga, Eric
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='tghqpi$150a$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--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).