From: Rick Frankel <rick@rickster.com>
To: emacs-orgmode@gnu.org
Subject: Re: controlling how htmlize fontifies code
Date: Mon, 3 Aug 2015 17:08:02 -0400 [thread overview]
Message-ID: <20150803210802.GA2327@eyeBook.home> (raw)
In-Reply-To: <87a8u8jxb0.fsf@ucl.ac.uk>
On Mon, Aug 03, 2015 at 02:50:27PM +0100, Eric S Fraga wrote:
> On Sunday, 2 Aug 2015 at 09:19, Rick Frankel wrote:
> > Check the documentation for the variable `org-html-htmlize-output-type'. Since
> > ox-reveal is derived from ox-html, it should work as specified. I personally
> > use ox-deck (also derived from html), so YMMV.
>
> On Sunday, 2 Aug 2015 at 09:41, Kaushal wrote:
> > I export with my custom Leuven theme (a light theme) css and it works fine.
> > I also have my emacs theme as a dark theme by default.
> >
> > ;; (setq org-html-htmlize-output-type 'inline-css) ; default
> > (setq org-html-htmlize-output-type 'css)
> > ;; (setq org-html-htmlize-font-prefix "") ; default
> > (setq org-html-htmlize-font-prefix "org-")
>
> 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?
Why wouldn't you expect local variables to work?
rick
next prev parent reply other threads:[~2015-08-03 21:08 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 [this message]
2015-08-04 12:41 ` Eric S Fraga
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=20150803210802.GA2327@eyeBook.home \
--to=rick@rickster.com \
--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).