From: Timothy <orgmode@tec.tecosaur.net>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: Timothy <orgmode@tec.tecosaur.net>,
"David Lukeš" <dafydd.lukes@gmail.com>,
"Max Nikulin" <manikulin@gmail.com>,
emacs-orgmode@gnu.org
Subject: Re: Code block syntax highlighting in async export
Date: Tue, 04 Oct 2022 12:14:19 +0800 [thread overview]
Message-ID: <87v8p0b4q2.fsf@tec.tecosaur.net> (raw)
In-Reply-To: <87y1twut3l.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 986 bytes --]
Hi Ihor,
>> Try it 😉
>
> You are right. With default preset, engrave-faces does not need to query
> Emacs about face colors and attributes and should not depend on the
> `display-graphic-p’.
Yep, it works because it’s basically implementing its own face-resolving layer.
This was originally done to allow exporting in a theme different to the one
currently being used as seamlessly as possible, it working with batch mode was a
bonus.
For the information of anyone else following the thread, you can easily add new
presets by creating an elisp setup file for batch mode and running `C-u M-x
engrave-faces-use-theme' in it — code defining a new preset will then be
generated and inserted at point.
All the best,
Timothy
--
Timothy (‘tecosaur’/‘TEC’), 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/tec>.
next prev parent reply other threads:[~2022-10-04 4:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-02 3:24 Code block syntax highlighting in async export David Lukeš
2022-10-02 7:24 ` Ihor Radchenko
2022-10-02 12:13 ` Max Nikulin
2022-10-03 12:08 ` David Lukeš
2022-10-03 12:42 ` Timothy
2022-10-03 13:22 ` David Lukeš
2022-10-03 13:58 ` Ihor Radchenko
2022-10-03 14:40 ` Timothy
2022-10-04 4:10 ` Ihor Radchenko
2022-10-04 4:14 ` Timothy [this message]
2022-10-03 15:57 ` Max Nikulin
2022-10-03 19:32 ` David Lukeš
2022-10-04 4:04 ` 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=87v8p0b4q2.fsf@tec.tecosaur.net \
--to=orgmode@tec.tecosaur.net \
--cc=dafydd.lukes@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@gmail.com \
--cc=yantar92@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).