From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: Again: MetaPost calling TeX
Date: Tue, 19 Jun 2001 17:58:52 +0200 [thread overview]
Message-ID: <3.0.6.32.20010619175852.01a73c90@server-1> (raw)
In-Reply-To: <20010617214628.A17333@ruhrau.de>
At 09:46 PM 6/17/01 +0200, Johannes Huesing wrote:
>Content-Type: text/plain; charset=iso-8859-1
>Content-Disposition: inline
>X-MIME-Autoconverted: from 8bit to quoted-printable by smail.let.uu.nl id
KAA04870
>
>Hi all,
>
>again I have problems with btex .. etex constructs within MetaPost
>files. Skimming old list messages I saw that this is often due to
>versions of ConTeXt and TeXExec out of sync. This was the case indeed
>so I installed the version of TeXExec that came with my ConTeXt (which
>I fetched ojn March 28th. After that, the messages "could not make mpx
>file" disappeared. Instead, I get messages of the kind that are
>attached along with a minimal example that led to the error message.
bug in beta, probably solved, if not ... do you use the betabeta?
>What am I doing wrong?
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
next prev parent reply other threads:[~2001-06-19 15:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-17 19:46 Johannes Huesing
2001-06-19 15:58 ` Hans Hagen [this message]
2001-06-20 15:40 ` Johannes Huesing
2001-06-20 17:18 ` Johannes Huesing
2001-06-21 3:48 ` Johannes Huesing
2001-06-20 21:43 ` Patrick Gundlach
2001-06-21 3:42 ` Johannes Huesing
2001-06-21 7:55 ` Hans Hagen
2001-06-21 13:16 ` Johannes Huesing
2001-06-21 13:57 ` Hans Hagen
2001-06-21 19:54 ` Johannes Huesing
2001-06-21 21:06 ` Johannes Huesing
2001-06-22 7:12 ` 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=3.0.6.32.20010619175852.01a73c90@server-1 \
--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).