emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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: Mon, 3 Oct 2022 22:57:16 +0700	[thread overview]
Message-ID: <a8932050-ef0b-1ff0-9bb2-7c73d9344265@gmail.com> (raw)
In-Reply-To: <CAEPTPEwLOy9-kXozuSkRcsrUR955uPsP=W5jtoqeM6EX4EECXQ@mail.gmail.com>

On 03/10/2022 19:08, David Lukeš wrote:
>> Could you please provide an example?
> 
>> 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
> 
> This looks indeed very similar, thank you! I'll investigate if I can
> leverage any of the workarounds mentioned.

I have realized that 
https://orgmode.org/worg/org-contrib/babel/languages/ob-doc-elisp.html 
has colorized source blocks. The file is created using 
https://git.sr.ht/~bzg/worg/blob/master/publish.sh and the script is 
executed inside a container with no available DISPLAY.


  parent reply	other threads:[~2022-10-03 16:39 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
2022-10-03 15:57       ` Max Nikulin [this message]
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=a8932050-ef0b-1ff0-9bb2-7c73d9344265@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).