From: Vikas Rawal <firstname.lastname@example.org>
To: Kyle Meyer <email@example.com>
Cc: org-mode mailing list <firstname.lastname@example.org>
Subject: Re: File local variables
Date: Fri, 12 Dec 2014 12:03:32 +0530 [thread overview]
Message-ID: <A7B9AB8B-F6DE-43AE-BD23-14E9D3AB2C7B@agrarianresearch.org> (raw)
>> 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?
> I can't confirm this either (using the following text).
> | # -*- org-export-babel-evaluate: nil; -*-
> | #+begin_src emacs-lisp :exports both
> | (message "Evaluating?")
> | #+end_src
> | #+RESULTS:
> | : Evaluating?
Thanks Aaron and Kyle.
I perhaps confused the fact that the line which started with a ; was showing up in the export to understand that the line was not being treated as it should.
But in my earlier org files, I always started this line with a ; and it used to work fine. Perhaps (perhaps), the behaviour has changed in terms of not treating lines starting with ; as comments in org.
Be that as it may, starting the line with a # works.
prev parent reply other threads:[~2014-12-12 6:33 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
2014-12-12 6:32 ` Kyle Meyer
2014-12-12 6:33 ` Vikas Rawal [this message]
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 \
* 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).