From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Notes and questions on 432 page book.
Date: Wed, 05 May 2004 14:07:29 +0200 [thread overview]
Message-ID: <6.0.1.1.2.20040505140542.01e7cda0@server-1> (raw)
In-Reply-To: <200405050640.02510.john@wexfordpress.com>
At 18:40 05/05/2004, you wrote:
>using the Eplain macros. If there is a way to single space
>the TOC using the regular Context macros I will be happy to
>eliminate the Eplain, which may solve some of the other
>problems.
what is single spacing a toc?
with regards to including eplain text, why not typesetting it as a separate
document, and then do something
\externalfigure[eplaintoc.pdf][width=\textwidth,height=\textheight]
Hans
next prev parent reply other threads:[~2004-05-05 12:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-05 16:40 John Culleton
2004-05-05 12:07 ` Hans Hagen [this message]
2004-05-05 20:00 ` John Culleton
2004-05-05 16:29 ` Hans Hagen
2004-05-06 5:16 ` John Culleton
2004-05-06 6:18 ` John Culleton
2004-05-06 5:12 ` Matthew Huggett
2004-05-06 21:34 ` John Culleton
2004-05-06 17:49 ` Hans Hagen
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=6.0.1.1.2.20040505140542.01e7cda0@server-1 \
--to=pragma@wxs.nl \
--cc=ntg-context@ntg.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).