From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Re: installing context with tetex
Date: Tue, 02 Dec 2003 09:59:05 +0100 [thread overview]
Message-ID: <6.0.0.22.2.20031202095747.020488c8@server-1> (raw)
In-Reply-To: <vines.sxdD+Nq2nzA@SZKOM.BFS.DE>
At 09:30 02/12/2003, you wrote:
>Hi patrick,
>just to explain WHY i got confused. I was looking at knuth.tex as a simple
>example. An *this* example contains no \startX or \stopX . So i got the
>impression that contex may not need them.
Hello World \end
would be Knuthian; this works ok in context, but, in many cases multiple
passes are needed and this triggered by \starttext .. \stoptext
Hans
next prev parent reply other threads:[~2003-12-02 8:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-02 8:30 Walter Harms
2003-12-02 8:59 ` Hans Hagen [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-01 15:17 Walter Harms
[not found] <vines.sxdD+,lklzA@SZKOM.BFS.DE>
2003-11-28 19:52 ` Peter Münster
[not found] <"vines.sxdD+,lklzA"@SZKOM.BFS.DE>
2003-11-28 9:44 ` Hans Hagen
2003-11-28 8:50 Walter Harms
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.0.22.2.20031202095747.020488c8@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).