From: Andrew Cagney <ac131313@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa/doc] tex -> texindex -> tex -> texindex -> tex
Date: Mon, 21 Jan 2002 10:59:00 -0000 [thread overview]
Message-ID: <3C4C64F8.10607@cygnus.com> (raw)
In-Reply-To: <Pine.SUN.3.91.1020121122030.17248A@is>
> On Mon, 21 Jan 2002, Andrew Cagney wrote:
>
>
>> Noticed that the texinfo 4.0 doco mentions that, when building
>> documentation, the sequence:
>>
>> tex
>> texindex
>> tex
>> texindex
>> tex
>>
>> should be used. The attached does this.
>
>
> Which begs a question: why don't we use texi2dvi, like God intended?
> I've seen quite a few documents where the tex/texindex duet is run
> more than 2 times, until the indices converge. Why should we
> second-guess a well-established tool such as texi2dvi?
Lost in history I suspect (I do remember very early on finding texi2dvi
unreliable or nonexistant?).
BTW, how do I get texi2dvi to run pdftex.
Andrew
next prev parent reply other threads:[~2002-01-21 18:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-21 0:35 Andrew Cagney
2002-01-21 2:23 ` Eli Zaretskii
2002-01-21 10:59 ` Andrew Cagney [this message]
2002-01-21 14:51 ` Andrew Cagney
2002-01-22 0:59 ` Eli Zaretskii
2002-01-22 8:37 ` Andrew Cagney
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=3C4C64F8.10607@cygnus.com \
--to=ac131313@cygnus.com \
--cc=eliz@is.elta.co.il \
--cc=gdb-patches@sources.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