Re: [O] Org-babel: can evaluation confirmation be disabled (e.g., set to always yes)?
Dear Nick, > It is documented in the Org manual, sec. 14.5, Evaluating code blocks, > footnote 1, which points you to sec. 15.4, Code evaluation and security > issues. Thanks for your help (and apologies for missing this footnote). Best, Torsten
Re: [O] Org-babel: can evaluation confirmation be disabled (e.g., set to always yes)?
It's under Miscellaneous in the manual. See the description of org-confirm-babel-evaluate at http://orgmode.org/manual/Code-evaluation-security.html#Code-evaluation-security Best, Ista On Thu, Jul 7, 2011 at 12:38 PM, Torsten Anders wrote: > Dear Babel developers, > > As you know, whenever I hit C-c C-c in a code block, I get the following > question. > > Evaluate this code block on your system? (y or n) > > In the case of "nested" calls (using noweb) there can even be many queries > like that before some code is actually executed. > > Can this be disabled by setting it to yes by default? I don't do any coding > in my blocks that could in any ways adversely affect my system... > > I could not find anything related in the documentation, apologies if I missed > it. > > Best, > Torsten > -- Ista Zahn Graduate student University of Rochester Department of Clinical and Social Psychology http://yourpsyche.org
Re: [O] Org-babel: can evaluation confirmation be disabled (e.g., set to always yes)?
Torsten Anders wrote: > Dear Babel developers, > > As you know, whenever I hit C-c C-c in a code block, I get the following > question. > > Evaluate this code block on your system? (y or n) > > In the case of "nested" calls (using noweb) there can even be many queries > like that before some code is actually executed. > > Can this be disabled by setting it to yes by default? I don't do any coding > in my blocks that could in any ways adversely affect my system... > > I could not find anything related in the documentation, apologies if I missed > it. > > Best, > Torsten It is documented in the Org manual, sec. 14.5, Evaluating code blocks, footnote 1, which points you to sec. 15.4, Code evaluation and security issues. Nick
