From: "Berend de Boer" <berend@pobox.com>
Cc: "Mailing List" <ntg-context@ntg.nl>
Subject: Re: mpost: cutbefore/cutafter
Date: Mon, 9 Oct 2000 20:51:32 +0200 [thread overview]
Message-ID: <006401c03221$f10637c0$0521a8c0@nederware.nl> (raw)
In-Reply-To: <3.0.6.32.20001007232627.008cf800@pop.wxs.nl>
> If members of this list don't want to be overloaded with metapost, we
may
> consider a dedicated metafun list.
It is sometimes hard to make the distinction. And MetaPost is becoming
an integral part of ConTeXt.
Groetjes,
Berend. (-:
next prev parent reply other threads:[~2000-10-09 18:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-06 11:12 Marc van Dongen
2000-10-07 21:26 ` Hans Hagen
2000-10-09 18:51 ` Berend de Boer [this message]
2000-10-09 19:34 ` metafun talk in ntg-context list (was Re: mpost: cutbefore/cutafter) Ed L Cashin
2000-10-09 19:55 ` metafun talk in ntg-context list (was Re: mpost:cutbefore/cutafter) Hans Fredrik Nordhaug
2000-10-09 20:07 ` metafun talk in ntg-context list (was Re: mpost: cutbefore/cutafter) Ed L Cashin
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='006401c03221$f10637c0$0521a8c0@nederware.nl' \
--to=berend@pobox.com \
--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).