emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: emacs-orgmode@gnu.org
Subject: Re: controlling how htmlize fontifies code
Date: Tue, 4 Aug 2015 13:41:45 +0100	[thread overview]
Message-ID: <87egjjfcom.fsf@ucl.ac.uk> (raw)
In-Reply-To: <20150803210802.GA2327@eyeBook.home> (Rick Frankel's message of "Mon, 3 Aug 2015 17:08:02 -0400")

On Monday,  3 Aug 2015 at 17:08, Rick Frankel wrote:

[...]

>> I have tried both setting a local variable and also using #+bind: but
>> neither approach works for some reason.  I did not expect the local
>> variable setting to work, of course.
>>
>
> Both should work. Are you sure you have `org-export-allow-bind-keywords' set?

I do allow bind keywords.  Strange.  I'll investigate further with emacs
-Q etc.  I may post an ECM later.

> Why wouldn't you expect local variables to work?

Because, if I understand correctly, the exporter processes the file into
a different buffer which is then exported and locally set variables
don't transfer to the new buffer.  This is why I have used binding in
the past.  Maybe the new exporter is different?

thanks,
eric

-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.2, Org release_8.3beta-1315-ga3b2b7

  reply	other threads:[~2015-08-04 12:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-02  9:24 controlling how htmlize fontifies code Eric S Fraga
2015-08-02 12:17 ` Rasmus
2015-08-03 13:51   ` Eric S Fraga
2015-08-02 13:19 ` Rick Frankel
2015-08-02 13:41   ` Kaushal
2015-08-03 13:50   ` Eric S Fraga
2015-08-03 21:08     ` Rick Frankel
2015-08-04 12:41       ` Eric S Fraga [this message]
2015-08-04 13:24       ` Eric S Fraga
2015-08-04 14:00         ` Rasmus
2015-08-04 15:09           ` Nicolas Goaziou
2015-08-04 15:21             ` Rasmus
2015-08-04 18:27               ` Nicolas Goaziou
2015-08-04 18:38                 ` Rasmus
2015-08-04 18:44                   ` Nicolas Goaziou
2015-08-04 16:03             ` Eric S Fraga

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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  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=87egjjfcom.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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).