Closed VladimirAlexiev closed 5 months ago
I think there's a problem here, in that there are elisp blocks of code that are used liberally for
Asking for user confirmation for elisp is therefore quite disturbing for the user. The following post, permit evaluation, indicates that one should be able to add :eval yes
to code blocks and thereby evade the confirmation for selected contents, but apparently it doesn't work. So this issue is one to come back to.
In e3b23c0f2f13baa62600043eb79edb05fad3bedb I removed the setting "allow anything". org-confirm-babel-evaluate
is set as a local variable inside an ontology document anyway.
Since the setting is buffer local, closing this as good enough.
A part of #3 is that
org-confirm-babel-evaluate nil
is unsafe.Here's what I have in my dot-emacs:
It's a bit over-complicated. We can just say that plantuml and sparql are safe: