From: dongdigua <dongdigua@outlook.com>
To: emacs-orgmode@gnu.org
Subject: [PATCH] org-faq.org: rename org-export-htmlize-* options to org-html-htmlize-*
Date: Wed, 07 Jun 2023 10:40:30 +0800 [thread overview]
Message-ID: <PS2P216MB1138F8C9932A00073597CE88A053A@PS2P216MB1138.KORP216.PROD.OUTLOOK.COM> (raw)
look at this commit:
https://git.sr.ht/~bzg/org-mode/commit/8134e80bdfb55bbce9aecf3f5958a2bd43cc0b63
the document didn't catch up with source code
I encountered this problem in:
https://emacs-china.org/t/org-emacs-script-org-publish-all/20782
and documented it in: https://dongdigua.github.io/org_export_highlight
--- a/org-faq.org
+++ b/org-faq.org
@@ -3793,7 +3793,7 @@
options or via global variables. See
[[https://orgmode.org/manual/Export-settings.html#Export-settings][this
section]] of the manual for a
full list.
-** How can I preserve faces when I export an agenda from the command
line?
+** How can I preserve faces when I export an org file from the command
line?
:PROPERTIES:
:CUSTOM_ID: preserving-faces-during-batch-export
:END:
@@ -3821,18 +3821,18 @@
definitions. If you'd like to use more complex styles, you'll have to
make sure that the export process only assigns classes instead of
direct color values. This can be done by binding the variable
-=org-export-htmlize-output-style= to =css= for the duration of the
+=org-html-htmlize-output-style= to =css= for the duration of the
export, for example with
: emacs -batch -l ~/.emacs
-: -eval '(let ((org-export-htmlize-generate-css (quote css)))
+: -eval '(let ((org-html-htmlize-generate-css (quote css)))
: (org-batch-agenda "e"))'
Then you can use a style file to make these classes look any way you
like. To generate face definitions for a CSS file based on any faces
you are currently using in Emacs, you can use the following command:
-: M-x org-export-htmlize-generate-css RET
+: M-x org-html-htmlize-generate-css RET
This will generate a =<style>...</style>= section, the content of
which you can add to your style file.
---
https://dongdigua.github.io
next reply other threads:[~2023-06-14 8:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 2:40 dongdigua [this message]
2023-06-14 12:22 ` [PATCH] org-faq.org: rename org-export-htmlize-* options to org-html-htmlize-* Ihor Radchenko
-- strict thread matches above, loose matches on Subject: below --
2023-06-28 15:29 dongdigua
2023-06-28 17:06 ` Ihor Radchenko
2024-04-04 11:27 ` Ihor Radchenko
2024-04-04 19:55 ` Rudolf Adamkovič
2024-04-05 13:58 ` Ihor Radchenko
2024-04-12 18:00 ` 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=PS2P216MB1138F8C9932A00073597CE88A053A@PS2P216MB1138.KORP216.PROD.OUTLOOK.COM \
--to=dongdigua@outlook.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 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).