From: Carsten Dominik <carsten.dominik@gmail.com>
To: Jason Dunsmore <emacs-orgmode@dunsmor.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] org-export-htmlize-output-type docstring patch
Date: Sat, 8 Jan 2011 19:01:15 +0100 [thread overview]
Message-ID: <50CA9488-17EC-4506-9FC6-AFFD573ABD64@gmail.com> (raw)
In-Reply-To: <87sjx8qp4a.fsf@riotblast.dunsmor.com>
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
prev parent reply other threads:[~2011-01-08 18:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-04 22:29 [PATCH] org-export-htmlize-output-type docstring patch Jason Dunsmore
2011-01-08 18:01 ` Carsten Dominik [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50CA9488-17EC-4506-9FC6-AFFD573ABD64@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@dunsmor.com \
--cc=emacs-orgmode@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.