On Thu, 12 Aug 2010 08:44:42 -0500, Erik Iverson wrote: > > Can you try setting it via setq (i.e., globally) and see what happens? > > On 08/12/2010 07:53 AM, Eric S Fraga wrote: > > Hello all, > > > > Back from a short holiday and trying to catch up on work... and so I > > may have missed something in the org mailing list (although I've > > searched...). > > > > I have a large file which includes many babel code blocks (mostly > > maxima) that I wish to have evaluated on export. This works except > > that I have to confirm each evaluation (which takes some time). I > > know that org-confirm-babel-evaluate exists so I have put the > > following at the top of my org file: > > > > # -*- org-confirm-babel-evaluate: nil; -*- [...] Erik, setting it globally (well, through customize as with setq didn't actually change the global value) works just fine so there must be some problem with the local value being ignored (I don't know enough about emacs variables to understand the distinction, at the level of lisp programming, between global and buffer local variables)? Of course, I'm not comfortable with the global setting for all the reasons already discussed on this list! Thanks for this, in any case, as it makes life a little less painful for today while I work on this long document! eric