On Sun, Jan 26, 2025 at 02:07:02PM +0200, Eli Zaretskii wrote:
> Suppose a project using Texinfo for its documentation does want to
> support older versions of makeinfo -- what would you suggest to use
> for that? It seems to me like makeinfo, being the tool that parses
> the Texinfo source, is in
On Sun, Jan 26, 2025 at 12:29:38AM +, 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 jus
On Sun, Jan 26, 2025 at 02:07:02PM +0200, Eli Zaretskii wrote:
> > > I'm open to other suggestions for how to avoid this problem. There was
> > > some confusion about whether this was a warning or an error, and whether
> > > it was "build-breaking", but that's possibly not relevant.
> >
> > It is
On Sun, Jan 26, 2025 at 11:26:48AM +, Pip Cet wrote:
> > We changed texinfo.tex to look ahead in the input and add a comma if one
> > was missing, so input like
>
> > As far as I remember, the warnings didn't stop the Info file from being
> > output.
>
> But the Info file would have (slightly
"Gavin Smith" writes:
> On Sun, Jan 26, 2025 at 12:29:38AM +, Pip Cet via Bug reports for the GNU
> Texinfo documentation system wrote:
>> This isn't as helpful a bug report as I would have liked. I tried
>> understanding this problem, but for reasons I cannot quite grasp yet it
>> was too
On Sun, Jan 26, 2025 at 07:32:17PM +0100, Patrice Dumas wrote:
> > @ifversion @atleast 10.1
> > ... stuff that only Texinfo 10.1 and newer supports ...
> > @end ifversion
>
> It seems to me that it can be done with @ifset and -D on the
> command-line.
>
> It could be
> @ifset version-atleast-1
> From: Gavin Smith
> Date: Sun, 26 Jan 2025 17:05:40 +
> Cc: pip...@protonmail.com, bug-texinfo@gnu.org
>
> Projects should declare a minimum version of texi2any to support for
> developers to use.
We did.
> The most reliable check of backwards compatibility
> is to actually test processin
> From: Gavin Smith
> Date: Sun, 26 Jan 2025 09:19:00 +
> Cc: bug-texinfo@gnu.org
>
> This is stated in the NEWS entry for Texinfo 6.1:
>
> 6.1 (06 February 2016)
>
> * Language:
> ...
> . For processing with TeX, a comma is automatically provided following
> a cross-reference command
On Sun, Jan 26, 2025 at 12:29:38AM +, Pip Cet via Bug reports for the GNU
Texinfo documentation system wrote:
> This isn't as helpful a bug report as I would have liked. I tried
> understanding this problem, but for reasons I cannot quite grasp yet it
> was too hard for me.
>
> My understand
