you are absolutely right: I did not know about system-wide header args. the following system-wide setting in the devel version is equivalent to my old setting:
(setq org-export-babel-evaluate t) (add-to-list 'org-babel-default-header-args '(:eval . "never-export")) thanks again for your help and patience! Thomas "Charles C. Berry" <ccbe...@ucsd.edu> writes: > On Fri, 30 Sep 2016, Thomas Alexander Gerds wrote: > >> right, this is what changed and setting :eval never-export on a each >> block solves the problem. however, the new way breaks all my >> existing org-code. > > I don't follow this. What exactly is broken? > > You know all the options for setting header args, right? System-wide, > buffer-wide, etc. For buffer-wide setting, one line is all it takes: > > : #+PROPERTY: header-args :eval never-export > > (and remember to C-c C-c on that line whenever you insert/edit it) > >> is there a reason why the header args have to be ignored when >> org-export-babel-evaluate is nil? or asking more directly: would it >> be possible to have another option, e.g., >> (setq org-export-babel-evaluate 'never-eval-obey-header-args) >> > > But that is what :eval never-export does. > >> such that the export process does never evaluate src code but header >> arguments are always obeyed? >> > > Possible, yes. But since it adds no new capability and makes the babel > code more involved, there isn't the motivtion to do it. > > Chuck > > > -- Thomas A. Gerds -- Department of Biostatistics Copenhagen University of Copenhagen, Oester Farimagsgade 5, 1014 Copenhagen, Denmark
