Ihor Radchenko writes:
> Maybe an alist? Either way is fine.
Yup, exactly what Org LaTeX does; it solves virtually the same problem.
> Then, it is probably Richard's turn to update the patch.
Go, Richard, go! :)
Rudy
--
"Mathematics takes us still further from what is human into the region
o
Rudolf Adamkovič writes:
> Yes, this is all we need:
>
> 1. Look up BACKEND in `org-latex-src-block-backend'
> 2. Look up LANG in `org-latex-BACKEND-langs'
Correction: `org-texinfo-*' instead of `org-latex-*', of course.
TL;DR We mirror what Org LaTeX does.
Rudy
--
"We shall not cease fro
Rudolf Adamkovič writes:
>> On the other hand, simply allowing to specify @example appears to be
>> safe (I may be wrong), even if we happen to use language name that is
>> not supported by the highlighter.
>
> Yes, this is all we need:
>
> 1. Look up BACKEND in `org-latex-src-block-backend'
>
Ihor Radchenko writes:
> ...
Apologies for a late reply. I have been sick. :(
> Also, keep in mind that syntax highlighting is experimental and that the
> texinfo manual explicitly says
>
> Warning: Source highlighting is experimental; feedback is
> welcomed. The syntax of HIGHLIGHT_
Rudolf Adamkovič writes:
> Here are some things we could do...
>
> OPTION 1: Keep it simple, if a bit messy:
>
> Rename `org-texinfo-listings-langs' to `org-texinfo-langs', and make
> sure all languages Org supports OOTB map correctly to Highlight,
> Pygments, and GNU Source Highlight. Per
Richard Sent writes:
> I added org-texinfo-listings-langs. I'm not super familiar with the Org
> codebase so I might've missed something, but as far as I can tell it's
> functionally correct.
In the case of `org-latex-listings-langs', the word "listings" refers to
the LaTeX package with the same
* lisp/ox-texinfo.el (org-texinfo-src-block): Preserve the language
field during export.
* etc/ORG-NEWS (Version 9.8): Add news entry.
* testing/lisp/test-ox-texinfo.el: Add tests.
---
Thanks for the feedback!
Rudolf Adamkovič writes:
> Ha! I have the exact same patch in works. I also asked on
