On Sun, Jan 26, 2025 at 12:29:38AM +0000, Pip Cet via Bug reports for the GNU Texinfo documentation system wrote: > Ideally, we would like to re-enable this warning when running new > versions of texinfo, so we can be sure not to break old builds, but I > haven't found a way to do so.
This is just a warning, so a code which triggers it on a past makeinfo version does not seems to be problematic to me? Anyway, I think that it is not a good idea to readd that warning for a the main processing, however I guess that it may be possible to readd a warning with a code that goes through the tree and determines if the warning situation applies. I would be ok with adding a TREE_TRANSFORMATIONS that does that if somebody volunteers to write the code, both in Perl and in C. > I understand the decision to drop the warning was deliberate, but > wouldn't it be possible to make it an optional warning, disabled by > default? The warning could indicate which version of texinfo stopped > warning about this by default and when it was released, so there would > be an incentive to disable the option at a future point. Maybe this could make sense for some disruptive changes, but this seems to me a lot of code for an issue that is not really problematic. I also do not see how this would be an incentive to disable the option at a future point, on the contrary, there could be a expectation that the warnings stays in for the foreseeable future. > While I have written an Emacs Lisp program to find such situations, I > think it would be much better to rely on standard texinfo to provide > warnings in this case. As I said above, if someone writes a TREE_TRANSFORMATIONS for that I would be ok to add it. -- Pat
