From: Max Nikulin <manikulin@gmail.com>
To: "David Lukeš" <dafydd.lukes@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Code block syntax highlighting in async export
Date: Sun, 2 Oct 2022 19:13:07 +0700 [thread overview]
Message-ID: <fe605f19-f9ef-9011-f88c-b5b76db0ceac@gmail.com> (raw)
In-Reply-To: <878rly1ydl.fsf@localhost>
On 02/10/2022 14:24, Ihor Radchenko wrote:
> David Lukeš writes:
>
>> I get different syntax highlighting in code blocks when using async
>> export: no colors, just bold, italics and underlines. Is this expected,
>> and if so, is there maybe an easy fix I just don’t know about?
>
> Could you please provide an example?
> See https://orgmode.org/manual/Feedback.html
>
>> I found a similar problem in [batch export], but the workaround seems
>> relatively complicated and brittle.
>
> That is likely a different problem. In batch mode, Emacs disabled
> font-lock-mode unconditionally, which makes fontification in some major
> modes broken.
Certainly more details is necessary, even export format (backend) is not
specified.
A problem that has some similar symptoms:
M. Pger. Re: no syntax highlighting for code blocks with org-publish.
Mon, 18 Jul 2022 22:55:15 +0000.
https://list.orgmode.org/inTtQOKWAhnFydjBE9fQOOdo_oV6kIPG5_E0d8DsfFiYMIJ4RNLRk68Id6dyrzy1qIDK8YJu0Wty7objv22vR31PNrh-qB9vKxMgHPxNAu8=@protonmail.com
next prev parent reply other threads:[~2022-10-02 12:21 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 [this message]
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
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=fe605f19-f9ef-9011-f88c-b5b76db0ceac@gmail.com \
--to=manikulin@gmail.com \
--cc=dafydd.lukes@gmail.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).