From: Tobias Burnus <burnus@gmx.de>
Cc: ntg-context <ntg-context@ntg.nl>
Subject: Re: getting context's version
Date: Wed, 18 Sep 2002 11:17:33 +0200 [thread overview]
Message-ID: <3D8844AD.6F42272D@gmx.de> (raw)
In-Reply-To: <Pine.LNX.4.42.0209181004250.1276-100000@servalys.nl>
Hi,
Wybo Dekker schrieb:
> > the method that taco posted is the way to go, since it's in the main
> > context file that i (when zipping) change the version number
>
> except that, if you unzip the newest cont-tmf and do mktexlsr but forget
> to regenerate the format, it tells that the new version is there, but the
> old one is actually run.
How about:
- check whether cont-en.efmt is older than context.tex
If this is the case, issue a warning/error
- check the version in context.tex
This catches also buried problems like fmt file older than texmf tree
which can also produce strange errors. (e.g. with cont-new.tex).
> So if I try to make a fool-proof script that needs the newer version, it
> would be nice to have the version from the format itself.
well using cont-en you got this number, unfortunally the fmt file is a
not that easily readable memory dump so you cannot easily grep for the
number directly without using TeX.
Tobias
--
This above all: To thine own self be true / And it must follow as
the night the day / Thou canst not then be false to any man.
next prev parent reply other threads:[~2002-09-18 9:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-17 10:07 Wybo Dekker
2002-09-17 18:00 ` Tobias Burnus
2002-09-17 18:23 ` Wybo Dekker
2002-09-18 6:57 ` Hans Hagen
2002-09-18 8:41 ` Tobias Burnus
2002-09-18 8:59 ` Wybo Dekker
2002-09-18 9:17 ` Tobias Burnus [this message]
2002-09-18 9:47 ` Taco Hoekwater
2002-09-18 15:28 ` Wybo Dekker
2002-09-19 18:41 ` Simon Pepping
2002-09-20 8:06 ` Taco Hoekwater
2002-05-20 8:56 ` Hans Hagen
2002-09-20 9:32 ` Tobias Burnus
2002-05-20 14:42 ` Hans Hagen
2002-09-20 17:55 ` Henning Hraban Ramm
2002-09-21 17:29 ` Simon Pepping
2002-09-18 9:43 ` Taco Hoekwater
2002-09-17 18:28 ` Taco
2002-09-17 21:20 ` Wybo Dekker
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=3D8844AD.6F42272D@gmx.de \
--to=burnus@gmx.de \
--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).