Re: asynchronous exporter and babel confirmation

[Achim Gratz <Stromeko@NexGo.DE>]

Nicolas Goaziou <n.goaziou <at> gmail.com> writes:
> Well, no, but its somewhat difficult to prevent it. Besides security
> considerations, even if we set `org-confirm-babel-evaluate' to nil
> during an asynchronous export, this won't handle the case of the user
> explicitly uses a :query keyword in a source block header.

Right.

> A very ugly hack would be to use:
> 
>  (defalias 'yes-or-no-p 'ignore)

Ugh.  I hope this won't be necessary.

I've recently refactored the evaluation check so it determines first whether the
code-block should be run and only in the affirmative checks if it should query
the user.  So it should be much easier now to have another dynamic binding for
preventing the question _and_ not run the block (as if the user had answered
"no", which is the only sensible choice when skipping the query).  It already
skips the query when the cached result is not stale (since it doesn't actually
run any code in this case).  


Regards,
Achim.