emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: controlling how htmlize fontifies code
Date: Sun, 02 Aug 2015 14:17:29 +0200	[thread overview]
Message-ID: <87wpxdsx46.fsf@gmx.us> (raw)
In-Reply-To: 874mkihwl2.fsf@ucl.ac.uk

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> 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?  

Check the functions disable-theme and load-theme in Emacs; maybe map
custom-enabled-themes over disable-theme. Check the hooks
org-export-before-processing-hook and org-export-before-parsing-hook in ox
to automate it.

Some people on SX seem to have used some JS coloring libraries.

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

This would also solve the problem when exporting in batch.  Patches
welcome.

Rasmus

-- 
I feel emotional landscapes they puzzle me

  reply	other threads:[~2015-08-02 12:17 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 [this message]
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=87wpxdsx46.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --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).