On 7/27/25 1:13 AM, Patrice Dumas wrote:
On Sat, Jul 26, 2025 at 02:42:59PM -0700, Raymond Toy wrote:
Or maybe texinfo run pygmentize with extra options?
Yes, pygmentize is especially called with -O noclasses=True, probably
because I wanted to avoid confusion with Texinfo classes.
Ahh, that explains it. Of course, a solution would be for texinfo to
prefix the classes with something to make it more unique. :-) Of course,
pygments could do the same too.
But I'm not asking for that. That would certainly break how Maxima
creates its database of links so the HTML file can be used for help
instead of plain text.
Anyway, since texinfo doesn't allow telling pygments what style to
use, I was thinking of solving this by updating the CSS with the
pgyments style that I want. This would also allow setting appropriate
colors for dark mode.
There was a discussion of a possibility to call syntax highlighting more
flexibly, and have users specify the command-line of syntax highlighting
commands. See this message, and, more generally this thread:
https://lists.gnu.org/archive/html/bug-texinfo/2024-11/msg00127.html
This is supposed to be implemented in the next release, maybe it could
fill your needs?
I didn't follow it completely, but it looks like it would work fine.
However, there is some work going on to make the Maxima HTML user manual
support dark mode because some users have requested it. I'd like to use
pygments to add syntax highlighting to the manual, and to support dark
mode I was going to use some dark mode style CSS to enable switching to
dark mode. If texinfo is going to inline the styles, that won't work, I
think.
​
