On Friday, 20 May 2016 at 16:45, Ken Mankoff wrote: > Eric: You're running something newer (by date) than the commit which > changed the behavior, which was: > > ec615b1 - Fix `org-export-babel-evaluate' handling (2016-04-28) > > But with all the branches in git, I don't know if you have that commit > or not. Anyway, I'm not sure why it works for you. It doesn't appear > to work for John and I the way it used to. Do you have a global "eval: > no" set somewhere?
I do have that commit incorporated in the version I am running from what I see in the git log. When I export, org asks whether to evaluate the code block and I respond with no. The existing results block is therefore exported but not changed. If I say yes, a new results block is generated and exported (and I can tell because it is different to what was there before). I have org-export-babel-evaluate set to t but also org-confirm-babel-evaluate to t. -- : Eric S Fraga (0xFFFCF67D), Emacs 25.0.92.1, Org release_8.3.4-775-g3308a5