From: Tom Tromey <tromey@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org
Subject: Re: RFA: fix gdb.texinfo for Texinfo 5.0
Date: Thu, 21 Feb 2013 18:52:00 -0000 [thread overview]
Message-ID: <87y5ehbitt.fsf@fleche.redhat.com> (raw)
In-Reply-To: <8338wpo946.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 21 Feb 2013 19:43:53 +0200")
>>>>> "Eli" == Eli Zaretskii <eliz@gnu.org> writes:
Tom> The fix for the first problem is to just remove the @table.
Tom> There's no need for it.
Eli> It's possible that someone used this trick to get the text indented.
Eli> All of those instances are around @defXXX directives, so perhaps
Eli> someone didn't like how functions/methods/etc. look unless indented.
Eli> But if you are satisfied by the results of removing @table in those
Eli> cases, that's fine by me.
Yeah, I think it looks ok.
Tom> The fix for the second was to use @w{} as the argument to @item.
Eli> Yes, Texinfo 5.0 replaced one ugly kludge with another, sigh.
Eli> (We left the @item empty because we wanted `' in the manual, by virtue
Eli> of "@table @samp".)
It took me a while to find @w{}.
Eli> P.S. I recommend everybody not to use makeinfo 5 yet, since it's
Eli> dog-slow. I renamed it to 'makeinfo5' and keep the old v4.13a
Eli> executable around, because it is 30 times faster, and that really
Eli> shows when processing such a large manual.
I noticed that too. It is really noticeably slower.
I just did this because Texinfo 5 is in the Fedora build root, and I
thought it would be good for gdb to be warning-free there.
Tom
next prev parent reply other threads:[~2013-02-21 18:52 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
2013-02-21 18:52 ` Tom Tromey [this message]
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=87y5ehbitt.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox