* [PATCH] org-export-htmlize-output-type docstring patch
@ 2011-01-04 22:29 Jason Dunsmore
2011-01-08 18:01 ` Carsten Dominik
0 siblings, 1 reply; 2+ messages in thread
From: Jason Dunsmore @ 2011-01-04 22:29 UTC (permalink / raw)
To: emacs-orgmode
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,
^ permalink raw reply related [flat|nested] 2+ messages in thread
* Re: [PATCH] org-export-htmlize-output-type docstring patch
2011-01-04 22:29 [PATCH] org-export-htmlize-output-type docstring patch Jason Dunsmore
@ 2011-01-08 18:01 ` Carsten Dominik
0 siblings, 0 replies; 2+ messages in thread
From: Carsten Dominik @ 2011-01-08 18:01 UTC (permalink / raw)
To: Jason Dunsmore; +Cc: emacs-orgmode
Applied, thanks.
- Carsten
On Jan 4, 2011, at 11:29 PM, Jason Dunsmore wrote:
> 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,
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-01-08 18:01 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2011-01-04 22:29 [PATCH] org-export-htmlize-output-type docstring patch Jason Dunsmore
2011-01-08 18:01 ` Carsten Dominik
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).