Re: per-file (or, really, per buffer) allowing/disallowing code block execution

[Max Nikulin <manikulin@gmail.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.