From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: seeking ConTeXt code
Date: Fri, 10 Sep 1999 18:13:24 +0200 [thread overview]
Message-ID: <37D92E24.EB1DD588@wxs.nl> (raw)
In-Reply-To: <vho671ihkia.fsf@jane.coe.uga.edu>
"Ed L. Cashin" wrote:
> Should I upgrade to the latest version or should I use Taco
> Hoekwater's suggestion to ignore the error messages and create an
> empty opt file? I am not as concerned with missing features as bugs:
> i.e., I could have the latest context on *my* machine for the
> features, with the teTeX rpms on other machines--if bugs are not an
> issue.
Well, you could add
clip: clip clip clip
to the command section in mult-com.tex and save yourself the trouble.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~1999-09-10 16:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-06 1:13 Ed L. Cashin
1999-09-06 19:26 ` Hans Hagen
1999-09-06 20:59 ` RH 6.0 teTeX (was Re: seeking ConTeXt code) (long) Ed L. Cashin
1999-09-07 7:54 ` Hans Hagen
1999-09-07 14:45 ` Ed L. Cashin
1999-09-08 3:08 ` seeking ConTeXt code Ed L. Cashin
1999-09-08 8:12 ` Hans Hagen
1999-09-09 0:01 ` Ed L. Cashin
1999-09-09 7:23 ` Hans Hagen
1999-09-13 20:33 ` Ed L. Cashin
1999-09-13 23:29 ` Hans Hagen
1999-09-08 8:35 ` Gilbert van den Dobbelsteen
1999-09-08 10:12 ` Hans Hagen
1999-09-09 8:37 ` Tobias Burnus
1999-09-08 12:11 ` Hans Hagen
1999-09-09 0:38 ` Ed L. Cashin
1999-09-09 7:13 ` Hans Hagen
1999-09-10 15:08 ` Ed L. Cashin
1999-09-10 16:13 ` Hans Hagen [this message]
1999-09-09 2:45 ` Ed L. Cashin
1999-09-09 7:04 ` Hans Hagen
1999-09-09 9:35 ` Hans Hagen
1999-09-09 9:37 ` Hans Hagen
1999-09-09 18:11 ` Berend de Boer
1999-09-09 10:05 ` Taco Hoekwater
1999-09-09 10:14 ` Taco Hoekwater
1999-09-09 10:26 ` Taco Hoekwater
1999-09-09 11:04 ` Taco Hoekwater
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=37D92E24.EB1DD588@wxs.nl \
--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).