From: Timothy <orgmode@tec.tecosaur.net>
To: "David Lukeš" <dafydd.lukes@gmail.com>
Cc: Max Nikulin <manikulin@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Code block syntax highlighting in async export
Date: Mon, 03 Oct 2022 20:42:11 +0800 [thread overview]
Message-ID: <87tu4ldqky.fsf@tec.tecosaur.net> (raw)
In-Reply-To: <CAEPTPEwLOy9-kXozuSkRcsrUR955uPsP=W5jtoqeM6EX4EECXQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]
Hi David,
> Sorry for that! I somehow thought that the issue would sound familiar
> to more seasoned Org users, and someone would come back with either
> “yeah, you need to do X” or “yeah, that’s a known limitation”.
Each backend is its own beast, somewhat 🙂.
> The export backend is HTML. In case anyone wants to try reproducing
> this, I made a minimal working example here:
> <https://github.com/dlukes/org-html-a-sync-export-syntax-highlighting>
> This looks indeed very similar, thank you! I’ll investigate if I can
> leverage any of the workarounds mentioned.
There’s a decent chance that `engrave-faces' (a package of mine that can now be
used for code blocks in LaTeX) will work in batch mode. Integrating it with
`ox-html', `ox-ansii', and `ox-odt' are all (distantly) on my todo list.
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-03 12:47 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 [this message]
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
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=87tu4ldqky.fsf@tec.tecosaur.net \
--to=orgmode@tec.tecosaur.net \
--cc=dafydd.lukes@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=manikulin@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).