[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Orgmode] [PATCH] org-export-htmlize-output-type docstring patch
From: |
Jason Dunsmore |
Subject: |
[Orgmode] [PATCH] org-export-htmlize-output-type docstring patch |
Date: |
Tue, 04 Jan 2011 16:29:41 -0600 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) |
The following message is a courtesy copy of an article
that has been posted to gmane.emacs.orgmode as well.
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. Here's a patch:
diff --git a/lisp/org-html.el b/lisp/org-html.el
index 03a5975..8981708 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,
- [Orgmode] [PATCH] org-export-htmlize-output-type docstring patch,
Jason Dunsmore <=