David Lukeš <dafydd.lu...@gmail.com> writes: >> I'll investigate if I can leverage any of the workarounds mentioned. > > So, for batch processing, avoiding --batch or --script and just using > --load with a script that either ends by killing Emacs, or killing it > via an additional --eval, works, i.e. syntax highlighting uses colors. > This was suggested in [1]. As [2] points out, adding -nw removes the > colors, and so does adding --daemon (suggested in [3]), so don't do > either. > > Enabling font-lock-mode manually and defining all the fontification > (see [4]) sounds like it would also work, but honestly, that's too > involved, so I didn't try it.
To clarify, the latest Org version should not care about font-lock being enabled. `font-lock-ensure' usually works in batch mode as well even though font-lock-mode is technically disabled. Except when it does not. Some major modes do fontification awkwardly, which can be considered a bug in those major modes. You can refer to https://yhetil.org/emacs-bugs/874jzdhh5m.fsf@localhost/ > Using an external colorizer (as shown in [5]), seems like a good > alternative, if non-Emacs dependencies are acceptable. > > These two last options can also be made to work with async export (my > original question), where you don't have control over how the batch > instance of Emacs is invoked. > >> 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. > > Sounds great! If it will work in regular batch mode, then it should > work with async as well :) I would not be so sure. If the issue is major-mode not doing fontification in batch mode, engrave-faces cannot do much. -- Ihor Radchenko // yantar92, 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/yantar92>
