From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Re:: \filbreak OK--TOC again--dupes in index.
Date: Sat, 01 May 2004 20:21:49 +0200 [thread overview]
Message-ID: <6.0.1.1.2.20040501201814.02862ec0@localhost> (raw)
In-Reply-To: <200405010824.51770.john@wexfordpress.com>
At 20:24 01/05/2004, you wrote:
>On Thursday 29 April 2004 10:10 pm, John Culleton wrote:
>
> > To make the eplain macros coexist with Context requires
> > commenting out one line in eplain.tex:
> > %\def^^L{\par}%
> >
> > What this line does I have no idea.
>
>Now I am told that It converts end of page characters (^L)
>to \par statements, and the extra ^ has something to do
>with making the statement non-outer. The error when using
>eplain with Context involves a category code problem which
>I don't comprehend but accept as gospel from those who do.
>A patch has been suggested by Karl Berry and will be
>implemented in eplain.tex in due course.
hm, the ^^ just tells tex that it's a control character
the definition indeed makes the command non-outer (simply because no \outer
prefix is used) as well as makes sure that
some text
<formfeed>
some text
is treated as two paragraphs
Hans
prev parent reply other threads:[~2004-05-01 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-30 8:10 John Culleton
2004-05-01 18:24 ` John Culleton
2004-05-01 18:21 ` Hans Hagen [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=6.0.1.1.2.20040501201814.02862ec0@localhost \
--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).