From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Re: metafun
Date: Wed, 23 Jun 2004 18:04:19 +0200 [thread overview]
Message-ID: <40D9AA03.2010803@wxs.nl> (raw)
In-Reply-To: <m2acyugtw2.fsf@levana.de>
Patrick Gundlach wrote:
>Hi,
>
>
>
>>but I don't understand...I downloaded cont-tmf.zip yesterday from
>>pragma-ade downloading page...
>>
>>is it not the right place/version?
>>
>>
>
>that is the only authorative(spelling?) place to download... There
>are mirrors, but I don't know how uptodate they are.
>
>The output you have sent me (private mail) showed that you use the
>latest ConTeXt texfiles, but the perl progam "texexec" was not
>updated.
>
>Did texexec --make --alone metafun work?
>
>
watch out: scripts are now under ../texmf*/scripts/context and no longer under ../texmf/context/ ; normally this should make no difference but ...
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:[~2004-06-23 16:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 15:03 metafun jimarin
[not found] ` <m2eko6gvg m.fsf@levana.de>
[not found] ` <40DA8D15. 4020205@wxs.nl>
2004-06-23 15:11 ` metafun Patrick Gundlach
2004-06-23 15:26 ` metafun jimarin
2004-06-23 15:45 ` metafun Patrick Gundlach
2004-06-23 15:55 ` metafun jimarin
2004-06-23 16:03 ` metafun Patrick Gundlach
2004-06-23 16:11 ` metafun Hans Hagen
2004-06-23 16:04 ` Hans Hagen [this message]
2004-06-24 8:13 ` metafun Hans Hagen
2004-06-24 12:17 ` updating context in cygwin by hand jimarin
2004-06-24 12:33 ` Patrick Gundlach
2004-06-24 14:23 ` jimarin
2004-06-25 8:29 ` Patrick Gundlach
2004-06-25 8:37 ` jimarin
2004-06-25 8:48 ` Patrick Gundlach
2004-06-25 9:11 ` jimarin
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=40D9AA03.2010803@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).