From: Hans Hagen <pragma@wxs.nl>
Cc: "'ntg-context@ntg.nl'" <ntg-context@ntg.nl>
Subject: Re: useMETAFUNformattrue
Date: Thu, 28 Sep 2000 01:05:39 +0200 [thread overview]
Message-ID: <3.0.6.32.20000928010539.0094b2d0@pop.wxs.nl> (raw)
In-Reply-To: <0F3313EC125AD311981100105AB3A75D4DBD4F@N0795.mdf.fvbb.de>
At 03:05 PM 9/27/00 +0200, Haseloff, Lutz wrote:
>Hi all,
>
>when i use \useMETAFUNformattrue metapost complains about unknown parameter
>"-progname=mpost"
>in the logfile i find:
>system(mpost -progname=mpost -mem=metafun colortest-mpgraph)...executed.
>i think it must be:
>system(mpost -mem=metafun colortest-mpgraph)...executed.
this indeed assumes web2c mpost, if needed you can redefine:
\def\executeMPOST#1%
{mpost
\ifcase\interactionmode -int=batchmode \fi
\ifuseMETAFUNformat -progname=mpost -mem=metafun \fi #1}
in your local syst-gen.tex and change it to miktex syntax. Maybe I should
make turn this into a special, and make a miktex driver. Must not forget
this.
>my file contains:
>
>\starttext
>\setupcolors[state=start]
>\startMPpage
>colorcircle(10cm,red,green,blue) ;
>\stopMPpage
>\stoptext
>
>I use miktex + pdfetex by Fabrice
eh, then why not use fabrices mpost? Has some nice fixes too [buffer
problems and better randomizer], i think that mpost from web2c can work ok
with miktex.
>is this a bug in texexec.pl?
texexec can be told not to pass the string (for miktex set MpPassString to
"")
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE
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
-------------------------------------------------------------------------
prev parent reply other threads:[~2000-09-27 23:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-27 13:05 useMETAFUNformattrue Haseloff, Lutz
2000-09-27 23:05 ` Hans Hagen [this message]
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.20000928010539.0094b2d0@pop.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).