From e703ea98232cf3c947a7d6520ee3efef53ea00e5 Mon Sep 17 00:00:00 2001 From: Jason Dunsmore Date: Wed, 5 Jan 2011 03:29:41 +0000 Subject: [PATCH] `org-export-htmlize-output-type' docstring patch I noticed the choices for org-export-htmlize-output-type aren't listed in its docstring. I had to load up the customize interface to see what the choices were. --- lisp/org-html.el | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/lisp/org-html.el b/lisp/org-html.el index e6f5ed5a9..312e716c4 100644 --- a/lisp/org-html.el +++ b/lisp/org-html.el @@ -499,8 +499,10 @@ a file." (defcustom org-export-htmlize-output-type 'inline-css "Output type to be used by htmlize when formatting code snippets. -We use as default `inline-css', in order to make the resulting -HTML self-containing. +Choices are `css', to export the CSS selectors only, or `inline-css', to +export the CSS attribute values inline in the HTML. We use as default +`inline-css', in order to make the resulting HTML self-containing. + However, this will fail when using Emacs in batch mode for export, because then no rich font definitions are in place. It will also not be good if people with different Emacs setup contribute HTML files to a website, -- 2.11.4.GIT