From: Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk>
Subject: version dates confuse me after upgrade
Date: Thu, 06 Apr 2006 01:21:10 -0400 [thread overview]
Message-ID: <E1FRMve-0003yS-Ie@approximate.corpus.cam.ac.uk> (raw)
I just upgraded following the instructions on the wiki, and wanted to
check that it went well and that the newer ones were being found --
always a nightmare subject in *TeX* with paths configurable by a
combination of environment variables, config files, and config files
chosen by other env variables. So:
$ texexec --version
TeXExec 5.4.3 - ConTeXt / PRAGMA ADE 1997-2005
texexec : TeXExec 5.4.3 - ConTeXt / PRAGMA ADE 1997-2005
texutil : TeXUtil 9.0.1 - ConTeXt / PRAGMA ADE 1992-2006
tex : pdfeTeX, 3.141592-1.21a-2.2 (Web2C 7.5.4)
context : ver: 2006.03.25 13:21
cont-en : ver: 2005.01.31 fmt: 2006.3.28 mes: english
Here is the version line in the output of 'texexec somerandomfile.tex':
ConTeXt ver: 2006.03.25 13:21 fmt: 2006.4.6 int: english mes: english
The context version date match what texexec --version produces (though
texexec doesn't give the fmt date). But what does the early cont-en
version date (2005.01.31) mean?
-Sanjoy
`A society of sheep must in time beget a government of wolves.'
- Bertrand de Jouvenal
next reply other threads:[~2006-04-06 5:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-06 5:21 Sanjoy Mahajan [this message]
2006-04-06 8:14 ` Hans Hagen
2006-04-06 15:38 ` Sanjoy Mahajan
2006-04-06 15:58 ` Hans Hagen
2006-04-06 16:06 ` Taco Hoekwater
2006-04-06 21:17 ` Gerben Wierda
2006-04-06 22:10 ` Taco Hoekwater
2006-04-06 22:31 ` Hans Hagen
2006-04-06 18:31 ` Sanjoy Mahajan
2006-04-06 19:36 ` Taco Hoekwater
2006-04-06 21:07 ` Thomas A. Schmitz
2006-04-07 20:31 ` Sanjoy Mahajan
2006-04-08 8:56 ` Hans Hagen
2006-04-08 12:01 ` Sanjoy Mahajan
2006-04-08 12:40 ` Hans Hagen
2006-04-06 20:40 ` Hans Hagen
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=E1FRMve-0003yS-Ie@approximate.corpus.cam.ac.uk \
--to=sanjoy@mrao.cam.ac.uk \
--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).