Eric Schulte schulte.eric at gmail.com writes:
There is no way to customize `org-confirm-evaluate' to achieve this
behavior, however it can be accomplished through creative use of the
:eval header argument, by using the `org-export-current-backend'
variable to inhibit evaluation during
Ken Williams ken.willi...@thomsonreuters.com writes:
Eric Schulte schulte.eric at gmail.com writes:
There is no way to customize `org-confirm-evaluate' to achieve this
behavior, however it can be accomplished through creative use of the
:eval header argument, by using the
Eric S Fraga e.fr...@ucl.ac.uk writes:
ken.willi...@thomsonreuters.com writes:
Hi,
I know from the manual that I can set 'org-confirm-babel-evaluate' to t,
or nil, or a function, to control whether I'm asked permission to run a
code block.
However, that only gives me two choices - ask
Hi,
I know from the manual that I can set 'org-confirm-babel-evaluate' to t,
or nil, or a function, to control whether I'm asked permission to run a
code block.
However, that only gives me two choices - ask the user, or pretend the
user said yes. Sometimes I'd like to pretend the user said no,
ken.willi...@thomsonreuters.com writes:
Hi,
I know from the manual that I can set 'org-confirm-babel-evaluate' to t,
or nil, or a function, to control whether I'm asked permission to run a
code block.
However, that only gives me two choices - ask the user, or pretend the
user said yes.
