Re: Code block syntax highlighting in async export

Hi Ihor, >> Try it  > > You are right. With default preset, engrave-faces does not need to query > Emacs about face colors and attributes and should not depend on the > `display-graphic-p’. Yep, it works because it’s basically implementing its own face-resolving layer. This was originally done

Re: Code block syntax highlighting in async export

Timothy writes: > Hi Ihor, > >> I would not be so sure. If the issue is major-mode not doing >> fontification in batch mode, engrave-faces cannot do much. > > Try it  You are right. With default preset, engrave-faces does not need to query Emacs about face colors and attributes and should not

Re: Code block syntax highlighting in async export

David Lukeš writes: >> Could you please provide an example? > >> Certainly more details is necessary, even export format (backend) is not >> specified. > > Sorry for that! I somehow thought that the issue would sound familiar > to more seasoned Org users, and someone would come back with either

Re: Code block syntax highlighting in async export

> 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. Well spotted! I

Re: Code block syntax highlighting in async export

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 +.

Re: Code block syntax highlighting in async export

Hi Ihor, > I would not be so sure. If the issue is major-mode not doing > fontification in batch mode, engrave-faces cannot do much. Try it  All the best, Timothy -- Timothy (‘tecosaur’/‘TEC’), Org mode contributor. Learn more about Org mode at . Support Org development

Re: Code block syntax highlighting in async export

David Lukeš 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

Re: Code block syntax highlighting in async export

> 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

Re: Code block syntax highlighting in async export

Hi David, > Sorry for that! I somehow thought that the issue would sound familiar > to more seasoned Org users, and someone would come back with either > “yeah, you need to do X” or “yeah, that’s a known limitation”. Each backend is its own beast, somewhat . > The export backend is HTML. In

Re: Code block syntax highlighting in async export

> Could you please provide an example? > Certainly more details is necessary, even export format (backend) is not > specified. Sorry for that! I somehow thought that the issue would sound familiar to more seasoned Org users, and someone would come back with either "yeah, you need to do X" or

Re: Code block syntax highlighting in async export

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

Re: Code block syntax highlighting in async export

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

Code block syntax highlighting in async export

Hi all, 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? I found a similar problem in [batch export], but the workaround seems relatively