Hello, "Charles C. Berry" <ccbe...@ucsd.edu> writes:
> On Fri, 11 Nov 2016, Frederick Giasson wrote: > >> Hi Chuck, >> >>> even with a minimal init file. >>> >>> If you ever set the value of `org-export-babel-evaluate' to nil >>> this might produce the behavior you describe. >> >> Maybe, but as stated in the manual: "Setting the >> org-export-babel-evaluate variable to nil will ensure that no code >> blocks are evaluated as part of the export process." > > Argh! That paragraph needs to be revised. Do you want to provide a patch for that? > Like the docstring says > > "Users who wish to avoid evaluating code on export should use the > header argument ‘:eval never-export’." > > It is tempting to `make-obsolete-variable' this variable and change > its name to something that more completely describes what does not > happen when set to nil. It can be done for Org 9.1. Regards, -- Nicolas Goaziou
