From: Johannes Huesing <hannes@ruhrau.de>
Subject: Re: Again: MetaPost calling TeX
Date: Thu, 21 Jun 2001 05:48:51 +0200 [thread overview]
Message-ID: <20010621054851.B666@ruhrau.de> (raw)
In-Reply-To: <20010620191841.A1742@ruhrau.de>; from hannes@ruhrau.de on Wed, Jun 20, 2001 at 07:18:41PM +0200
Here is the log of the MetaPost run again.
-----8-<-------
Randomizer initialized to 398035626.This is MetaPost, Version 0.641 (Web2C 7.3.1)
(mpgraph.mp (/usr/local/share/texmf/metapost/context/mp-tool.mp)
(/usr/local/share/texmf/metapost/context/mp-spec.mp)
(/usr/local/share/texmf/metapost/context/mp-grph.mp)
(/usr/local/share/texmf/metapost/context/mp-page.mp)
(/usr/local/share/texmf/metapost/context/mp-core.mp)
! mpx file ended unexpectedly.
l.13
?
-----8-<-------
Line 13 in the mpgraph.mp file contains:
graphictextdirective "\global \loadfontdefinitionfileoncetrue " ;
and graphoctextdirective is defined in the mp-grph.mp module as
follows:
def graphictextdirective text t =
graphictextstring := graphictextstring & t & CRLF ;
enddef ;
so all that happens is the extension of graphicstextstring by
the argument of graphictextdirective and a CRLF. I don't
understand why this interferes with the .mpx file at that
moment.
Greetings
Johannes
--
Johannes Hüsing | Domain: Adresse im Internet. Besteht aus einem
hannes@ruhrau.de| technischen Teil (http://www.), einem Namen
| (erwin_meier) und einer Endung (zum Beispiel
| .de für Deutschland) [J. Albrecht, "Zeit" 12/2001]
next prev parent reply other threads:[~2001-06-21 3:48 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
2001-06-20 15:40 ` Johannes Huesing
2001-06-20 17:18 ` Johannes Huesing
2001-06-21 3:48 ` Johannes Huesing [this message]
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=20010621054851.B666@ruhrau.de \
--to=hannes@ruhrau.de \
--cc=johannes.huesing@ruhrau.de \
/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).