> On Aug 3, 2017, at 1:04 AM, Uwe Brauer <o...@mat.ucm.es> wrote: > > > > I just checked and situation is absurd. Here is the minimal example: > [snip] > > When I set org-export-babel-evaluate nil, then the code is *not* > evaluated, *but* the code block *and* the result are exported. > [snip] > When I set org-export-babel-evaluate to t, export but say no to the > question whether or not to evaluate, *only* the result is exported, > which is what I want. > > Is this a *bug*? I wait a day, then I will file a bug report.
No. It is *obsolete* and its replacement is not recommended for your application. ,----[ C-h v org-export-babel-evaluate RET ] | org-export-babel-evaluate is a variable defined in ‘org-compat.el’. | Its value is t | | This variable is an alias for ‘org-export-use-babel’. | This variable is obsolete since Org 9.1; | use ‘org-export-use-babel’ instead. | | Documentation: | Switch controlling code evaluation and header processing during export. | When set to nil no code will be evaluated as part of the export | process and no header arguments will be obeyed. When set to | ‘inline-only’, only inline code blocks will be executed. Users | who wish to avoid evaluating code on export should use the header | argument ‘:eval never-export’. | | You can customize this variable. | | [back] `---- You want `:eval never-export'. Chuck
