From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kelvin Hu Subject: Fwd: Question: how to disable htmlize during exporting? Date: Tue, 25 Mar 2014 20:29:55 +0800 Message-ID: References: <87lhvyelbo.fsf@bzg.ath.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:43919) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WSQUQ-0002FD-B1 for emacs-orgmode@gnu.org; Tue, 25 Mar 2014 08:29:59 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WSQUP-0003kH-DC for emacs-orgmode@gnu.org; Tue, 25 Mar 2014 08:29:58 -0400 Received: from mail-lb0-x232.google.com ([2a00:1450:4010:c04::232]:42045) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WSQUP-0003kB-5t for emacs-orgmode@gnu.org; Tue, 25 Mar 2014 08:29:57 -0400 Received: by mail-lb0-f178.google.com with SMTP id s7so307913lbd.9 for ; Tue, 25 Mar 2014 05:29:56 -0700 (PDT) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org [forwarding to mailing-list] ---------- Forwarded message ---------- From: Kelvin Hu Date: 2014-03-25 18:07 GMT+08:00 Subject: Re: Question: how to disable htmlize during exporting? To: Bastien Hi Bastien, 2014-03-25 16:25 GMT+08:00 Bastien : > 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. Thanks for your reply, I have tried this approach, but it reports "error: (void function nil)". Per the definition in `ox-html.el', it must be either 'inline-css or 'css. After some research, now I use the following workaround: (flet ((org-html-fontify-code (code lang) (when code (org-html-encode-plain-text code)))) ;; code here ;; e.g. (insert (org-export-as 'html nil nil t nil)) ) Redefine the function `org-html-fontify-code' will help, but I think this workaround is a little ugly. So, I hope this feature can be disabled gracefully, like set `org-html-htmlize-output-type' to nil.