I solved the issue by creating the following bash script in my project folder:
#!/bin/sh TERM=xterm export TERM emacs -q -nw --load=build.el --eval="(eval-buffer)" --eval="(save-buffers-kill-terminal)" This avoid using --script (and thus batch) and thus allows font-lock to be enabled when my publishing elisp script (build.el) is run. Thanks to `TERM=xterm export TERM`, this bash script can be run from the Emacs shell (otherwise problematic because of the -nw option). To have 'extended' syntax highlighting for R, note that I have to load ESS from build.el. Hope this will help! Thanks again for your feedback and your insights. Best, M ------- Original Message ------- On Wednesday, July 20th, 2022 at 12:33 AM, Tim Cross <theophil...@gmail.com> wrote: > "M. Pger" mp...@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-0fd2dbaac...@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-0fd2dbaac...@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.
