From: Bart Schaefer <schaefer@brasslantern.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: Zsh hackers list <zsh-workers@zsh.org>, dana <dana@dana.is>
Subject: Re: PATCH: Fix node references and menu (was Re: Yodl 4 required?)
Date: Thu, 21 Apr 2022 14:34:07 -0700 [thread overview]
Message-ID: <CAH+w=7YNx=cUqo0pDh18NaFLAFjXE7yVeP3DenbFSacGouTFQg@mail.gmail.com> (raw)
In-Reply-To: <20220410220707.GH27526@tarpaulin.shahaf.local2>
On Sun, Apr 10, 2022 at 3:07 PM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>
> Bart Schaefer wrote on Sun, Mar 13, 2022 at 21:00:16 -0700:
> > On Sun, Mar 13, 2022 at 8:34 PM Bart Schaefer <schaefer@brasslantern.com> wrote:
> > >
> > > makeinfo (GNU texinfo) 4.8 fails
> > > texi2any (GNU texinfo) 6.7 works
> >
> > This repairs the cross-references. texi2any seems to be too
> > forgiving, because these really were wrong.
>
> Sorry for the breakage and thanks for fixing this. What should I do
> differently next time?
Seems to come down to:
1) If you add new texinode(this)(next)(prev)(up) entries, the (up)
section needs a startmenu()/endmenu() that references each of the
(this).
2) If there is a sect(thing) or subsect(thing) following the
texinode(this), (thing) must be exactly the same as (this).
There are probably nuances I'm missing, but the above is what fixed
the errors from the old makeinfo.
> I had built the documentation (all formats)
> before pushing that, and here (Debian) «make info» still passes on
> master if I locally revert your fix.
At some point the texi packages re-implemented "makeinfo" in terms of texi2any.
texi2any is supposed to warn about missing cross-references unless the
--no-validate flag is passed, but it doesn't catch all the same ones
that the older makeinfo does.
> I guess I should try to build on a more bleeding-edge distro (e.g., in
> Debian sid)?
Unless texi2any has been fixed, using a newer distro is not going to
help ... you need an older one.
prev parent reply other threads:[~2022-04-21 21:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-13 21:22 Yodl 4 required? Bart Schaefer
2022-03-14 1:56 ` dana
2022-03-14 3:34 ` Bart Schaefer
2022-03-14 4:00 ` PATCH: Fix node references and menu (was Re: Yodl 4 required?) Bart Schaefer
2022-04-10 22:07 ` Daniel Shahaf
2022-04-21 21:34 ` Bart Schaefer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH+w=7YNx=cUqo0pDh18NaFLAFjXE7yVeP3DenbFSacGouTFQg@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=d.s@daniel.shahaf.name \
--cc=dana@dana.is \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).