From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: fix gdb.texinfo for Texinfo 5.0
Date: Thu, 21 Feb 2013 17:44:00 -0000 [thread overview]
Message-ID: <8338wpo946.fsf@gnu.org> (raw)
In-Reply-To: <877gm1d7nm.fsf@fleche.redhat.com>
> From: Tom Tromey <tromey@redhat.com>
> Date: Thu, 21 Feb 2013 08:10:53 -0700
>
> I tried Texinfo 5.0 on gdb.texinfo today, and it gave a number of
> warnings.
>
> These fell into two major categories: first, we were using @table
> without any @items; and second, we were using @item without an argument.
>
> The fix for the first problem is to just remove the @table.
> There's no need for it.
It's possible that someone used this trick to get the text indented.
All of those instances are around @defXXX directives, so perhaps
someone didn't like how functions/methods/etc. look unless indented.
But if you are satisfied by the results of removing @table in those
cases, that's fine by me.
> The fix for the second was to use @w{} as the argument to @item.
Yes, Texinfo 5.0 replaced one ugly kludge with another, sigh.
(We left the @item empty because we wanted `' in the manual, by virtue
of "@table @samp".)
> This patch fixes all the problems.
Thanks!
> Tested by rebuilding with makeinfo 5.0 and makeinfo 4.13.
>
> Ok?
Yes, thanks.
P.S. I recommend everybody not to use makeinfo 5 yet, since it's
dog-slow. I renamed it to 'makeinfo5' and keep the old v4.13a
executable around, because it is 30 times faster, and that really
shows when processing such a large manual.
next prev parent reply other threads:[~2013-02-21 17:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-21 15:11 Tom Tromey
2013-02-21 17:44 ` Eli Zaretskii [this message]
2013-02-21 18:52 ` Tom Tromey
2013-02-21 19:07 ` Eli Zaretskii
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=8338wpo946.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox