emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Aaron Ecay <aaronecay@gmail.com>
To: Vikas Rawal <vikaslists@agrarianresearch.org>,
	org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: File local variables
Date: Fri, 12 Dec 2014 00:01:09 -0500	[thread overview]
Message-ID: <87y4qd31ii.fsf@gmail.com> (raw)
In-Reply-To: <D9B52FD1-47F5-4042-B201-32DD0485CBAE@agrarianresearch.org>

Hi Vikas,

2014ko abenudak 11an, Vikas Rawal-ek idatzi zuen:
>> I used to disable evaluation of source code when exporting by using the following as the first line:
>> ;; -*- mode: Org; org-export-babel-evaluate: nil; -*-
>> This is not working any more. Has something changed?
>> My org-version is: Org-mode version 8.3beta (release_8.3beta-614-gc10ae1 @ /Users/vikas/.emacs.d/src/org-mode/lisp/)
>> Vikas
> I think this is a bug. Could somebody confirm.

I can’t confirm, in the sense that including that line in a file sets
the buffer-local value of org-export-babel-evaluate to nil.

If that variable isn’t having the effect of suppressing evaluation, that
sounds like a bug, but it’s not clear that that is what is going on.
Can you send an ECM?

> The following line shows up in the Latex export.
> ; -*- mode: org; org-export-babel-evaluate: nil -*-

That is because ; is the comment syntax for (e)lisp.  You probably want
to begin the line with # instead.

Aaron Ecay

  reply	other threads:[~2014-12-12  5:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-08 10:03 File local variables Vikas Rawal
2014-12-12  4:51 ` Vikas Rawal
2014-12-12  5:01   ` Aaron Ecay [this message]
2014-12-12  6:32     ` Kyle Meyer
2014-12-12  6:33       ` Vikas Rawal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y4qd31ii.fsf@gmail.com \
    --to=aaronecay@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=vikaslists@agrarianresearch.org \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).