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: controlling how htmlize fontifies code
Date: Sun, 2 Aug 2015 10:24:25 +0100	[thread overview]
Message-ID: <874mkihwl2.fsf@ucl.ac.uk> (raw)

Hello all,

I have to prepare a whole new set of lectures for a new course and I
thought I would play around with =ox-reveal= as an HTML export target
may actually be more appropriate for this course than my usual PDF
target.  And one of the best features of org is that most of the effort
is the same regardless of target so I won't be wasting much time
playing! :-)

In playing around with reveal, I realised that exporting code uses the
=ox-html= exporter (obvious, in hindsight).  This exporter uses emacs's
own fontifying engine to colour code for export.  My problem is that I
use a dark background theme for emacs but want presentations to be based
on a light background.  The code colouring, as a result, is completely
wrong.

Now, I can simply start up emacs with a light background, export my
slides and everything is fine.  However, it would be nice to not have to
start up a new emacs just for this.  Is there an easy way to pretend,
for export to HTML, that emacs is using a light background?  Maybe a way
to advise the exporter?  

Thanks,
eric

PS - ideally, code export to HTML would make use of CSS instead of
     hard-coding in the colours but that's a discussion for another
     day...
-- 
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.2, Org release_8.3beta-1303-g3f0398

             reply	other threads:[~2015-08-02  9:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-02  9:24 Eric S Fraga [this message]
2015-08-02 12:17 ` controlling how htmlize fontifies code 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
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=874mkihwl2.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).