From: "John R. Culleton" <john@wexfordpress.com>
Cc: Willi Egger <w.egger@boede.nl>
Subject: Re: Disappearing TOC.
Date: Tue, 7 Mar 2006 17:00:10 -0500 [thread overview]
Message-ID: <200603071700.10682.john@wexfordpress.com> (raw)
In-Reply-To: <440DBFC4.8020606@boede.nl>
On Tuesday 07 March 2006 12:15, Willi Egger wrote:
> Hi John,
>
> I believe this has to do with the arranging! So run texexec without
> arranging first. Check that the TOC is there.
> Herafter run texexec again, this time with arranging and run it only once.
>
> I hope this helps!
>
> Willi
>
Bingo! I am so used to running e.g., plain tex twice to get the
TOC etc. to work that I did it automatically. Your rule works.
My bad habit didn't.
This is worth a note in the manual, if it is redone at some
future time.
--
John Culleton
Books with answers to marketing and publishing questions:
http://wexfordpress.com/tex/shortlist.pdf
Book coaches, consultants and packagers:
http://wexfordpress.com/tex/packagers.pdf
prev parent reply other threads:[~2006-03-07 22:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-07 15:45 John R. Culleton
2006-03-07 17:15 ` Willi Egger
2006-03-07 22:00 ` John R. Culleton [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=200603071700.10682.john@wexfordpress.com \
--to=john@wexfordpress.com \
--cc=ntg-context@ntg.nl \
--cc=w.egger@boede.nl \
/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;
as well as URLs for NNTP newsgroup(s).