From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: controlling how htmlize fontifies code
Date: Tue, 04 Aug 2015 17:21:45 +0200 [thread overview]
Message-ID: <87y4hrqdti.fsf@gmx.us> (raw)
In-Reply-To: 87h9ofgkej.fsf@nicolasgoaziou.fr
Hi,
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Not really, although I would write it like the following instead:
>
> (let ((output-type org-html-htmlize-output-type)
> (font-prefix org-html-htmlize-font-prefix))
> (with-temp-buffer
> ...
> ;; Htmlize region.
> (let ((org-html-htmlize-output-type output-type)
> (org-html-htmlize-font-prefix font-prefix))
> (org-html-htmlize-region-for-paste
> (point-min) (point-max)))))
That might be ascetically nicer.
>> Of course, in org-html--build-head the mysterious :html-htmlized-css-url
>> is required so you won't actually get any default colors, which is a bit
>> boring in my opinion. I don't know if I'm misunderstanding
>> :html-htmlized-css-url, a bug or something supposed to be set via a
>> publish project.
>
> I think there's a bug. `org-org-htmlized-css-url' is defined in
> "ox-org.el", but not attached to any info property. So, at the
> moment, :html-htmlized-css-url is bogus.
Do we have a function that can generate a candidate css file for
org-org-htmlized-css-url or :html-htmlize-css-url?
Rasmus
--
Lasciate ogni speranza o voi che entrate: siete nella mani di'machellaio
next prev parent reply other threads:[~2015-08-04 15:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-02 9:24 controlling how htmlize fontifies code Eric S Fraga
2015-08-02 12:17 ` Rasmus
2015-08-03 13:51 ` Eric S Fraga
2015-08-02 13:19 ` Rick Frankel
2015-08-02 13:41 ` Kaushal
2015-08-03 13:50 ` Eric S Fraga
2015-08-03 21:08 ` Rick Frankel
2015-08-04 12:41 ` Eric S Fraga
2015-08-04 13:24 ` Eric S Fraga
2015-08-04 14:00 ` Rasmus
2015-08-04 15:09 ` Nicolas Goaziou
2015-08-04 15:21 ` Rasmus [this message]
2015-08-04 18:27 ` Nicolas Goaziou
2015-08-04 18:38 ` Rasmus
2015-08-04 18:44 ` Nicolas Goaziou
2015-08-04 16:03 ` Eric S Fraga
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y4hrqdti.fsf@gmx.us \
--to=rasmus@gmx.us \
--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 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).