From: Ihor Radchenko <yantar92@posteo.net>
To: Mehul Sanghvi <mehul.sanghvi@gmail.com>
Cc: ML Emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [BUG] html-htmlize-output-type does not work on a per project basis [9.6.15 (release_9.6.15 @ /usr/local/share/emacs/29.3/lisp/org/)]
Date: Sat, 15 Jun 2024 13:32:10 +0000 [thread overview]
Message-ID: <87ikyagwmd.fsf@localhost> (raw)
In-Reply-To: <CAPo9-A9q=q-mLZnCioqKh=0Kn+Mma2=OFHQg3QMV6LiRHsEOyw@mail.gmail.com>
Mehul Sanghvi <mehul.sanghvi@gmail.com> writes:
> I would like to be able to set =:html-htmlize-output-type= on a
> per-project basis. That does not seem to be working. If I have
> ~htmlize.el~ installed and set =:html-htmlize-output-type css=, then I
> get hardcoded values for the colours being used in the code blocks. If
> I don't have ~htmlize.el~ installed, I get plain text. To get CSS class
> names, I have to do an explicit =(setq org-html-htmlize-output-type
> 'css)= which effects all publishing projects.
>
>
> 1. What exactly did you do?
>
> I set =:html-htmlize-output-type css= in the _blog-non-prod_ project.
> I also set =:html-htmlize-output-type 'css= and then tried both values
> with =htmlize-output-type= as well.
ox-html does not currently support setting :html-htmlize-output-type
option. Only variable `org-html-htmlize-output-type' is supported.
Same for `org-html-htmlize-font-prefix'.
It would be nice to change this, yes.
Confirmed.
Patches welcome!
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-06-15 13:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 16:22 [BUG] html-htmlize-output-type does not work on a per project basis [9.6.15 (release_9.6.15 @ /usr/local/share/emacs/29.3/lisp/org/)] Mehul Sanghvi
2024-06-15 13:32 ` Ihor Radchenko [this message]
2024-06-17 17:44 ` Mehul Sanghvi
2024-06-17 17:49 ` Ihor Radchenko
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=87ikyagwmd.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=mehul.sanghvi@gmail.com \
/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).