From: Hans Hagen <pragma@wxs.nl>
Subject: Re: ConTeXt Errors
Date: Thu, 06 Apr 2006 22:44:51 +0200 [thread overview]
Message-ID: <44357DC3.7060803@wxs.nl> (raw)
In-Reply-To: <F4AAE2E381F0624BB8F513C1E9880FB93CDBB2@newman.fwb.internal.srs.com>
Browder, Tom wrote:
> ! Undefined control sequence.
> l.14 \newcontextversion
> {2006.03.25 13:21}
>
Next time that you update, this macro does some checking on a mismatch between a format and an update, so that may help resolve future update problems
in general, the more recent versions have more provisions for checking
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.com
| www.pragma-pod.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~2006-04-06 20:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-06 17:36 Browder, Tom
2006-04-06 18:38 ` Renaud AUBIN
2006-04-06 20:41 ` Hans Hagen
2006-04-06 19:41 ` Taco Hoekwater
2006-04-06 20:44 ` Hans Hagen [this message]
2006-04-06 17:42 Browder, Tom
2006-04-07 13:40 Browder, Tom
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=44357DC3.7060803@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).