On Thu, Mar 20, 2025 at 11:20:39PM +0100, Rudolf Adamkovič wrote: > Patrice Dumas <pertu...@free.fr> writes: > > > Indeed, the current way of doing syntax highlighting is not customizable > > enough. There is a plan to change how this is done as discussed in the > > theread started by this mail: > > https://lists.gnu.org/archive/html/bug-texinfo/2024-11/msg00109.html > > That is good to know. I hope it the patch will get in and a new version > of Texinfo will be released soon thereafter. :)
This is indeed something that is planned for the next release, but there is probably a long way to go for the next release... > I have one more question about syntax highlighting, if you have a minute > for me. If a user writes `@example python', for instance, in their file > and then uses older Texinfo, will it choke on the `python' argument, or > will it ignore it? I tested with 5.0 and there is nothing output. I checked the development code and there is a warning. So, at worse it should be a warning, though I think that it is not possible, as I think that the argument to @example was implemented in 6.8 before the warning was added, probably in 7.0. This could be an issue for other block @-command getting arguments, for instance @cartouche argument is quite new, and would probably trigger a warning on 7.0. And it should happen in the future for more releases if we change more block @-commands to have arguments. Also there is nothing that would allow to know in the Texinfo code whether the block commands has an argument or not. -- Pat
