emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Kelvin Hu <ini.kelvin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Question: how to disable htmlize during exporting?
Date: Tue, 25 Mar 2014 09:25:47 +0100	[thread overview]
Message-ID: <87lhvyelbo.fsf@bzg.ath.cx> (raw)
In-Reply-To: <CAO61DjwgB+vr4x8Jb6TXi18TXxU-epbTuHUBTQrvrUctnjUM6A@mail.gmail.com>	(Kelvin Hu's message of "Tue, 25 Mar 2014 11:33:44 +0800")

Hi Kelvin,

Kelvin Hu <ini.kelvin@gmail.com> writes:

> Org is awesome and now I use it as my blogging tool, everything is
> perfect except the source code highlighting. Org uses htmlize.el to
> highlight source code, it's fine, but when I use another theme or on a
> different machine, the generated html(contains source code block) will
> change due to Emacs theme change. As I use git to manage my generated
> html files, so when publishing after a theme change, those html files
> contain source code will change and thus I need to *git commit* a lot
> of files without actual useful content change!

> So now I want to use google prettify.js to highlight my source code,
> but I cannot disable htmlize.el during exporting, I googled and
> someone said removing htmlize.el will achieve this, but I don't think
> it is a good idea.

I'd try to set `org-html-htmlize-output-type' to nil but I didn't
test.  If it does not work, this is a bug.

-- 
 Bastien

  reply	other threads:[~2014-03-25  8:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-25  3:33 Question: how to disable htmlize during exporting? Kelvin Hu
2014-03-25  8:25 ` Bastien [this message]
     [not found]   ` <CAO61DjxKttv80o3pMN3Z2ZNORDRYw5j=E_eKrT0wiGypdWdSxg@mail.gmail.com>
2014-03-25 12:29     ` Fwd: " Kelvin Hu
2014-03-25 15:37       ` Rick Frankel
2014-03-25 15:41         ` Bastien

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=87lhvyelbo.fsf@bzg.ath.cx \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=ini.kelvin@gmail.com \
    /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).