From: Tim Cross <theophilusx@gmail.com>
To: "M. Pger" <mpger@protonmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: no syntax highlighting for code blocks with org-publish
Date: Wed, 20 Jul 2022 08:33:42 +1000 [thread overview]
Message-ID: <86edygg24y.fsf@gmail.com> (raw)
In-Reply-To: <wxaUFiqi8BmIPv8pcYRVHAFa0hTzM35roQxpVVRkgddjRkesPGX1kVBL3G0fr42FonlRq5FNjapV8RiovXV-RGEDehXn-cmIebf4HWBhzIQ=@protonmail.com>
"M. Pger" <mpger@protonmail.com> writes:
> I tried to publish using `M-x org-publish RET <name_of_project> RET` as you suggested, and
> syntax highlighting was actually implemented, thanks.
>
> Actually the problem is coming from the fact that I use `emacs -Q --script build.el` (as a
> bash script) to publish the project. According to
> https://list.orgmode.org/AE5693F1-F63D-4383-8840-0FD2DBAAC5D6@gmail.com/ (rather old, but
> apparently this has not changed), font-lock-mode is not enabled by default in --batch
> mode. Since `--script` "run Emacs in batch mode, like ‘--batch’, and then read and execute
> the Lisp code in file" (cf the doc), it seems that this is exactly my problem.
>
> A workaround is suggested in
> https://list.orgmode.org/AE5693F1-F63D-4383-8840-0FD2DBAAC5D6@gmail.com/, but
> unfortunately for me it does not work (yet). I am going to dig further into that.
>
I would be interested to hear how you go. I have a use case coming up
where I need to publish a large number of org files using a batch job,
so expect to run into the same issue. Right now, I'm still getting my
head around how to best get a consistent style when the input comes from
multiple org files from different sources and I want to minimise editing
the sources, plus provide a simple way to update/change the styling
later.
next prev parent reply other threads:[~2022-07-19 22:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 17:24 no syntax highlighting for code blocks with org-publish M. Pger
2022-07-17 23:42 ` Ihor Radchenko
2022-07-18 8:57 ` M. Pger
2022-07-18 21:50 ` Tim Cross
2022-07-18 22:55 ` M. Pger
2022-07-19 7:51 ` Tim Cross
2022-07-19 15:34 ` M. Pger
2022-07-19 22:33 ` Tim Cross [this message]
2022-07-19 23:14 ` M. Pger
2022-07-20 5:22 ` M. Pger
2022-07-21 11:38 ` 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=86edygg24y.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mpger@protonmail.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).